by Jake Dallimore.
Hmmm. That code is still present in 4.1.6, so unless it's removed locally, or there's a bug in it, I can't immediately see what might cause this error to resurface. Are you able to debug that site?