Just verified 2.7.1.62 STILL HAS THIS SAME ISSUE.
I also switched back to 2.5.0.66 that works properly. Thanks for the hint about this.
Just verified 2.7.1.62 STILL HAS THIS SAME ISSUE.
I also switched back to 2.5.0.66 that works properly. Thanks for the hint about this.