That seems to do the trick, cheers. I'll use this if I can't get an official fix added into the framework.
I wonder, did you get the fix?
Apparently it will be fixed in 4.1.0.
US: 1 (800) 212-2802
Join our mailing list