With some variations of upgrading CMS, installing modules and restoring databases, I got into a place where trying to add user properties for a new group was getting an error to the effect of
"column count doesn't match value count" in row [blah, blah...]
Sure enough, it was trying to do an INSERT with 5 values, and when I looked in the table "module_feusers_grouppropmap", it only had 4 columns. Some more quick looking showed that in the FEU method.upgrade.php, the upgrade to v1.3 had a call to add a 5th column to that table. So, my database was using a pre-1.3 table, while the rest of FEU thought it had been upgraded -- hence the error I was seeing.
What I couldn't figure out was: Is there any way through the CMS admin interface to force FEU to go through the upgrade process again? There was nothing on the Modules or ModuleManager pages.
I finally just used phpMyAdmin to manually add the 5th column, and all seems to be working okay. However, I'm worried that the call to AddcolumnSQL done by the upgrade module might also have updated some other DataDictionary table somewhere??
Lew
[solved]Mismatched versions of FEU module & FEU db table - how to force upgrade?
[solved]Mismatched versions of FEU module & FEU db table - how to force upgrade?
Last edited by Lew on Tue Jan 15, 2008 8:39 am, edited 1 time in total.
-
calguy1000
- Support Guru

- Posts: 8169
- Joined: Tue Oct 19, 2004 6:44 pm
Re: Mismatched versions of FEU module & FEU db table - how to force upgrade?
If you're very careful and know what you're doing you can alter the appropriate row of the cms_modules table with phpmyadmin or some other sql tool. This would do the trick for you.
Follow me on twitter
Please post system information from "Extensions >> System Information" (there is a bbcode option) on all posts asking for assistance.
--------------------
If you can't bother explaining your problem well, you shouldn't expect much in the way of assistance.
Please post system information from "Extensions >> System Information" (there is a bbcode option) on all posts asking for assistance.
--------------------
If you can't bother explaining your problem well, you shouldn't expect much in the way of assistance.
Re: Mismatched versions of FEU module & FEU db table - how to force upgrade?
Thanks Robert.
It still seems to be working fine, so I guess I knew what I was doing, was careful enough and was lucky!
Lew
It still seems to be working fine, so I guess I knew what I was doing, was careful enough and was lucky!
Lew
-
pgoneill
Re: [solved]Mismatched versions of FEU module & FEU db table - how to force upgr
I'm having the same problem. What's the column that's created there - I can't figure it out what the "I" means. I take it "lostunflag" is the new column name?
Re: [solved]Mismatched versions of FEU module & FEU db table - how to force upgrade?
Yes, the field to be added is lostunflag; Here's my ending table structure:
Field Type Attributes Null Default Extra Action
name varchar(40) No
group_id int(11) No 0
sort_key int(11) Yes NULL
required int(11) Yes NULL
lostunflag int(11) Yes NULL
Lew
Field Type Attributes Null Default Extra Action
name varchar(40) No
group_id int(11) No 0
sort_key int(11) Yes NULL
required int(11) Yes NULL
lostunflag int(11) Yes NULL
Lew
Re: [solved]Mismatched versions of FEU module & FEU db table - how to force upgr
hi,
i have a same probleme but with more !
see link here : http://forum.cmsmadesimple.org/index.ph ... 0.html#new
i have a same probleme but with more !
see link here : http://forum.cmsmadesimple.org/index.ph ... 0.html#new

