Everything was running fine, and then after a MySQL upgrade from 5.0 to 5.1 and then 5.5, which was somewhat faulty (some table prefixes were messed up and a little bit of data was lost but nothing major), we have had this new issue arise out of the blue.Everything was running fine, and then after a M