by Carol Hampton.
Has this now been fixed?
I am having the same problem in 2.6.2 but notice the build number looks slightly earlier, please could you let me know which version and build it was fixed in?
Thanks Carol