The Kunena team has announce the arrival of Kunena 7.0.4 [K 7.0.4] in stable which is now available for download as a native Joomla extension for J! 5.4.x/6.0.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.
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.
I think this isn't going to work as my site has been upgraded and live on J4 for about a week now; I thought we could do this on the J4 site. We have an online shop and had new users with transactions etc. since that update. Because of the relatively active shop, we had to do the update on a live situation, following the upgrade instructions (that for whatever reason failed) after encountering issues on the dev site when we didn't follow those instructions.
I don't think I can go back to the old backup of all the J3 users and then lose some of those that registered and shopped in the meantime. I will probably just make the forum page something else - copy and paste the old Q&A into a document of some kind and then decide what to do about Kunena; start over perhaps.
You would if you can run the old joomla 3 locally on your pc/laptop
with wamp or xampp .
Then again try to Upgrade to Joomla 4 and Kunena version 6 in the right way.
If that worked out well, you can only do it with phpmyadmin
Export all Kunena tables
and you can then put it back in your current version.
So then you don't touch the regular Joomla user
And if you can work with Wamp or xampp server
then you can also update your current website/shop
run in it as well (just make different database names but keep the same prefix .)
I often do this myself in this way to convert old forums
to the new version
