I have run the Update structure on Both Joomla CMS and Admin Tools. There appears to be an issue on The ID columns in the Admin Tools tables (attatched image), even after running the update structure process.
We're not the developers of that extension so you'll need to contact them regarding that. You should only need to run Joomla's database check followed by CBs within CB > Tools. If still having issues installing CB after running those then please PM (see link in my forum signature below) backend super user login credentials after creating a backup of your site and will attempt to debug this further.
Kyle (Krileon) Community Builder Team Member Before posting on forums:
Read FAQ thoroughly
+
Read our Documentation
+
Search the forums CB links:
Documentation
-
Localization
-
CB Quickstart
-
CB Paid Subscriptions
-
Add-Ons
-
Forge
-- If you are a Professional, Developer, or CB Paid Subscriptions subscriber and have a support issue please always post in your respective support forums for best results!
-- If I've missed your support post with a delay of 3 days or greater and are a Professional, Developer, or CBSubs subscriber please
send me a private message
with your thread and will reply when possible!
-- Please note I am available Monday - Friday from 8:00 AM CST to 4:00 PM CST. I am away on weekends (Saturday and Sunday) and if I've missed your post on or before a weekend after business hours please wait for the next following business day (Monday) and will get to your issue as soon as possible, thank you.
-- My role here is to provide guidance and assistance. I cannot provide custom code for each custom requirement. Please do not inquire me about custom development.
Looking deeper, we've seen that CB is expecting the __comprofiler table to be InnoDB - however we had to change it to MyISAM due to the number of columns our client wanted to store against profiles. Prior updates don't seem to have complained about this before. Is there any way to allow the new update to proceed whilst retaining the storage engine as MyISAM?
Your entire Joomla database should be InnoDB. It being MyISAM is a problem for Joomla and CB. Joomla has not used MyISAM since Joomla 3.x. I recommend converting the entire database and after doing so ensure your collations on every table and column are properly set to utf8mb4_unicode_ci.
Kyle (Krileon) Community Builder Team Member Before posting on forums:
Read FAQ thoroughly
+
Read our Documentation
+
Search the forums CB links:
Documentation
-
Localization
-
CB Quickstart
-
CB Paid Subscriptions
-
Add-Ons
-
Forge
-- If you are a Professional, Developer, or CB Paid Subscriptions subscriber and have a support issue please always post in your respective support forums for best results!
-- If I've missed your support post with a delay of 3 days or greater and are a Professional, Developer, or CBSubs subscriber please
send me a private message
with your thread and will reply when possible!
-- Please note I am available Monday - Friday from 8:00 AM CST to 4:00 PM CST. I am away on weekends (Saturday and Sunday) and if I've missed your post on or before a weekend after business hours please wait for the next following business day (Monday) and will get to your issue as soon as possible, thank you.
-- My role here is to provide guidance and assistance. I cannot provide custom code for each custom requirement. Please do not inquire me about custom development.
krileon
