The Kunena team has announce the arrival of Kunena 7.0.7 [K 7.0.7] in stable which is now available for download as a native Joomla extension for J! 5.4.x/6.0.x./6.1.x. This version addresses most of the issues that were discovered in K 6.2 / K 6.3 / K 6.4 and issues discovered during the last development stages of K 7.0
This section is for questions directly related to the procedure for installing Kunena for the first time or upgrading from an older version of Kunena.
Use this category:
to ask how to install or upgrade; or
if you encountered problems during the installation or upgrade procedure.
Use a different category to ask questions about problems that you may be having after you successfully installed or upgraded the currently supported version. If you are unsure what is the current supported version of Kunena, please go to the
download
page.
I followed your explanation.
With the exception that after kunena version 6 I was uninstalled.
I first imported the old kunena V5 data .sql.
And I also saw in Maintenance: Global Check-in that category table of kunena had to be checked in there.
but further your adjustments in categories and ranks
done and yes I must say then it does indeed work.
But then it is also to be hoped that one will also be there somewhere
the old kunena v5 media files is called saved so
one can still use it.
Can we please try to solve the problems one by one? It is simply too exhausting when various errors are to be fixed in a single topic.
The fact that you can't open themes is probably because no categories are published. I've noticed that categories that are not published still show as published in the backend. Publish some categories and then try to create a topic.
By the way: The database collation for Joomla 4.x and Kunena 6.x should be utf8mb4_unicode_ci or utf8mb4_general_ci.
Important! Always create a backup before you make any changes to your website!
Thank you. I am unable to create any categories to publish on the back end. No pre-existing categories made it through the update, and the back end gives the error each time I try on the back end. I added my observations of what was happening on the front-end to give some perspective that would perhaps give further insight.
I'm sure that the primary cause behind all of is that the categories did not survive the upgrade, despite doing our best to uninstall on the J3 site and install as per the documentation.
Thanks for noting the correct database collation - is there a script one can run via phpmyadmin to update this perhaps? Or would it just be better to uninstall K6.1.x and try to install it afresh again, or is it likely to lose the entire history in that scenario?
You can set the collation by clicking on "Operations" at the top and then scrolling all the way down. At Collation click the pulldown menu and scroll all the way down and select unicode_ci or general_ci under utf8mb4.
Below that click "Change all table collations" and if you want also "Change all column collations". Then click on OK in the lower right corner.
Then wait until the message appears that the character set has been changed. With large databases this can take a moment.
