Hi,
Good catch!
This is fixed in 4.2.0 already, and I will fix it for the next 4.1 stable release (4.1.7).
Hi,
Good catch!
This is fixed in 4.2.0 already, and I will fix it for the next 4.1 stable release (4.1.7).