by Jake Dallimore.
Hi Eric,
That code is still in place in the current 4.1.x stable branch, but of course it could be something else going on causing an error. What error are you seeing? What steps do you take before seeing it?
Thanks