Thanks for pointing this out – we’ll investigate.
We’ll fix this for our next release.
It’s already in beta for customers with support/subscription. But I don’t know when it will be finally released.
Is this problem fixed in latest release (2.6.2)? Please let me know so that we can upgrade.
Not 2.6.x, you need 3.0 for this fix.
When is 3.0 expected to be released? And is it certain that it will have this issue fixed?
Did you try the beta kit announced last month in this forum?
We’re doing final testing on the official 3.0 kits.