[SOLVED] J3.2, CB1.9.1 error 1062, cannot login front or back

updated a 3.1.5 site to 3.2 today (did one successfully yesterday). I went in and saved the joomla user strong passwords as in the other thread.

I get this error when I try to log into the front or the back:


1062
Error: 1062

Duplicate entry '62-8' for key 'PRIMARY' SQL=INSERT INTO wqlf_user_usergroup_map (user_id,group_id) VALUES (62,

not sure if it's a CB error or Joomla. I tried to repair the sessions table but it says the engine is not compatible with repair.

I can delete the line in the session table where userid = 62 and then I can at least access the site, but can't login

I don't think that has anything to do with CB. Especially if it's happening on backend login too. You likely have a 3rd party system, user, or authentication plugin installed that isn't compatible with J3.2. Rename 3rd party system, user , and authentication plugin folders within /plugins/TYPE/3rdpartyplugin to see if one of them maybe causing problems.

none of the 3rd party plugins in those folders look like culprits, but I'll try them one by one. I'm trying to think of which plugins fire in front and backend though. not many

Check your database table _user_usergroup_map and just manually remove the duplicate entry (be sure to create a backup of your database first). Then attempt to login a few times and see if issue resolved. If still not resolved then something is trying to add a usergroup over and over that already exists for the user.

there was already only one entry for userid = 62 so I deleted it. When I tried to log in the site gave me this warning:

Warning

You cannot access the private section of this site.

I then added back the entry in the table and get the same error again.

renaming all of the non-Joomla plugins in those folders didn't help unfortunately

I have no idea then. Something is trying to assign a usergroup that already exists for the user for some odd reason. If it affects backend Joomla login then it has nothing to do with CB as CB doesn't do anything on Joomla login triggers or on backend login. The only thing that could affect those locations is Joomla it self or a Joomla plugin that's acting on those triggers. You can see if CBSubs is doing it, unlikely, by disabling its content bot and then it can't act on Joomla.