- Posts: 8
- Thank you received: 0
Kunena 7.0.6 & Kunena 6.4.12 – Security Updates Released
The Kunena team has announce the arrival of Kunena 7.0.6 [K 7.0.6] 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.
The Kunena team is also pleased to announce the twelfth version of Kunena 6.4, a native Joomla extension for Joomla! 5.0, 5.1, 5.2, 5.3, 5.4 and 6.0.
Bug Unknown column "allreadtime" in "field list" after update to 4.03
Please Log in or Create an account to join the conversation.
the field allreadtime is missing in the table #__kunena_user_categories, you can add it:
I don't provide support by PM, because this can be useful for someone else.
Please Log in or Create an account to join the conversation.
Thanks in advance!
Ronald
Please Log in or Create an account to join the conversation.
This is really difficult to explain and I am constrained in what I tell you by the rules of this forum .rpfacts64 wrote: I am not so familiar with adding SQL to a table. Can you tell me how to do that please?
If you manually modify your Joomla database, in any way, you run the risk of destroying not only your Kunena data but also your entire Joomla website.
The query that xillibit wrote is only half complete.
Yes, using a tool like myPhpAdmin (you will probably find this in your webhost cPanel) can help. Unless you are skilled in running SQL queries against a database you may discover that it's not as easy as you had hoped.
I do not know why you had the error message to begin with when you attempted to upgrade from K 3.0.8 to K 4.0.3. This should not have occurred.
However, given my own experiences upgrading from K 3.0.8 to K 4.0.x, nothing really surprises me these days.
My recommendation is that you revert your site to the backup you made before you attempted to upgrade to K 4.0.3. If I was in your situation, I would then check and double-check that you have (a) met all the technical requirements to be able to use K 4.0.3, (b) checked the integrity of your Kunena database tables (possibly using the tools in phpMyAdmin before you attempt to upgrade to K 4.0.3. I would also refresh my knowledge about how to upgrade to K 4.0 (except that this information is a little out-of-date and discussed to how to update to K 3.0; it also does not explain how to downgrade from K 4.0 to K 3.0).
Blue Eagle vs. Crypsis reference guide
Read my blog and
Please Log in or Create an account to join the conversation.
support.hostgator.com/articles/specializ...ueries-in-phpmyadmin
Please Log in or Create an account to join the conversation.
Thanks for the help
regards Ronald
Please Log in or Create an account to join the conversation.