Thanks, I will update to the latest version. It seems strange though that if the issue was resolved with v2.7.3 then how would it be present in v4.1.6.
Great, thanks!
Ok, thanks very much. Could you remove the previous link please?
Any news on this?
Thanks