I think it could be best characterized as "problems using deprecated methods in a third-party module", but it could also be fairly characterized as "how the heck did this ever work in the first place?" We think the previous fix may have been to revert to an older version of the module.
no subject