Snog
Well-known member
While I have this marked as 2.1, I believe the same thing might be happening in 2.0. And I'm not sure if this is a bug in XF or not because I've been unable to track it down.
Sometimes (not always) after an upgrade, setting options and some fields added to tables the database become unavailable until they are saved again.
I had this happen with the upgrade to 2.1 Beta 6 and I simply re-saved the info and it became available again. But after I did that, I smacked myself for not checking if the values were in the database node table or not.
Just now an add-on stopped working in XF 2.0 for a client because a setting appeared to be empty in the options to the php code, but there were values in the option settings. All I did was save the options and once again it started working without a problem.
Has anyone else experienced anything like this? It's driving me nuts!
EDIT: It's almost as if add-ons are being disabled during an upgrade, and after the upgrade the defaults for the values are being used (even if values exist) until they are re-saved.
Sometimes (not always) after an upgrade, setting options and some fields added to tables the database become unavailable until they are saved again.
I had this happen with the upgrade to 2.1 Beta 6 and I simply re-saved the info and it became available again. But after I did that, I smacked myself for not checking if the values were in the database node table or not.
Just now an add-on stopped working in XF 2.0 for a client because a setting appeared to be empty in the options to the php code, but there were values in the option settings. All I did was save the options and once again it started working without a problem.
Has anyone else experienced anything like this? It's driving me nuts!
EDIT: It's almost as if add-ons are being disabled during an upgrade, and after the upgrade the defaults for the values are being used (even if values exist) until they are re-saved.
Last edited:
