update error

Since trying to update to CB 2.4.7+2020.11.17.19.46.40.33d80913c I get the error "Duplicate entry '8' for key 'PRIMARY'.
The same when I try CB 2.4.7+build.2020.11.19.14.24.58.59e8c0858.
Did anyone get the same issue?

Try running Joomla database fix tool within Extensions > Manage > Database. Next run the database fix tools within CB > Tools. Once done retry. I am not able to reproduce your issue, but that usually happens because something broke the auto increment parameter of a database table and things started inserting into reserved table ids.

Thank you Kyle,
The problem must be related to the fact that I imported field, tab and user list structure from my old site that still runs CB version 2.4.5 into my new site that ran 2.4.6. The CB tool found many errors in Tab ID's that needed to be changed. I backed up and used the CB repair option and that fixed the problem. I now have successfully upgraded to 2.4.7.

I am still cautious about going with this configuration as I exported and imported between CB 2.4.5 and 2.4.6. My old site has some software issues (unrelated to CB) and I would only try to upgrade CB there if I can find version 2.4.6.

Alternative is to reconstruct the CB structure on the new site manually. I will sleep on it.

Thanks a lot for your powerful advice! I really appreciate that.

Ngā mihi,

Erik.

I get the same error for weeks now.

"001_pkg_communitybuilder_2.4.7+build.2020.12.17.19.36.18.b7cc1f577.zip failed to install! hide
Duplicate entry '8' for key 'PRIMARY'"

No idea how to fix it.

You've a broken database structure more than likely. This is usually caused by manually tampering with the database and breaking the auto increment value for core database tables. This results in something installing trying to use a reserved id.

Enable debug mode and maximum error reporting then extra CB itself from the zip from the /extensions/packages folder. Now install that raw zip within Joomlas extension manager. This should hopefully expose the error more so you can see what exactly is failing. Without knowing what database table this is happening against there isn't much more I can suggest.