CMS Made Simple Forums

I have two installs of CMSMS on the web server - I took a version that was one or two versions old, duplicated it and upgraded to 1.11.7. A bit more functionality was added to this dev install, and all was (and still is!) working fine. When I replaced the live version with the dev version (so they are now duplicates), everything seemed to be fine, until we tried to add a new FEU, and we got the following error: Here's the odd thing - the dev version doesn't throw the error, and they are nearly identical - in fact, all that's different on dev now is that I've added JM_Forum. And just to test things, I added it to the live site this morning to see if it was a factor - no dice.

I won't list it all, but I'm running (on both):
CMSMS 1.11.7
FEU 1.21.15
CGExtensions 1.34
CMSMailer 5.2.1

I see that both FEU and CGExtensions have new versions, so I'll try those next, but any thoughts on why two nearly identical versions would have errors on only one?

tophers wrote:When I replaced the live version with the dev version (so they are now duplicates)

Sorry if it's a silly question but when you did that, did you replace the database too? If not, that might explain your error message (database was updated with additional column(s) during upgrade).

Probably barking up the wrong tree though.

It may seem silly, but believe me, it's happened! I replaced everything, including the database. Let me correct that - it looks like the version.php file didn't make it, because the live version was still showing version 1.11.3. I updated it and it displayed the correct version, with no change to the functionality. I did upgrade the modules in question and got everything working.

However, I had some strange behavior, which I tracked down to some naming issues - after the updates I had: both show up in Group Permissions (discovered when my client told me she had lost all access to FEU). Adding the duplicate to her permissions fixed the issue. But do I now have the CMS thinking there are two versions of FEU running?

And of course none of this answers the 'why did it stop working in the first place' question that started this thread.