You have to uninstall Kunena before migrating to Joomla 4. Then install Kunena again once on Joomla 4. Kunena isn't compatible with 3 and 4 at the same time like CB is. Kunena will detect your database on re-install though and deal with migration. That's what we had to do anyway during our internal migration for Joomlapolis.
I've no idea whether your error is from Kunena or CB or not though. You'd have to provide the full callstack for the error that shows what file it occurred in.
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.
Thanks, I uninstalled and then reinstalled it but saw errors like "Specified key is too long; Max key length is 1000 bytes" during the reinstall. The table conversion appears to have failed. I have a post on Kunena's forum as well but thought I'd check here just in case there was other insight.
You'll have to figure that out with Kunena. We're not Kunena's developer. That error though usually means a database table index is too long.
It being limited to 1000 bytes though is strange as that's really low and far below MySQL innodb defaults (which is 3072 bytes). Suggest contacting your host and having them fix that. Might just be a matter of fixing your table collations since you're coming from Joomla 3 you'll probably have to. Can generally do this from phpmyadmin under the Operations tab using the below.
Table options
Collation: utf8mb4_unicode_ci
Change all column collations: CHECKED
Maybe your database tables are still set to MyISAM and not Innodb? Can again fix that in phpmyadmin. Sorry, don't know what more to suggest as we're not Kunena's developer and you'll need to let them know.
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.
Thanks for the additional insight on the byte limit error. I will have a closer look at the tables as you suggested. To clarify all Joomla 4 tables need to be utf8mb4_unicode_ci collation?