Kunena 6.0.8 Released (17 Jan 2023)
The Kunena team has announce the arrival of Kunena 6.0.8 [K 6.0.8] which is now available for download as a native Joomla extension for J! 4.2.x. This version addresses most of the issues that were discovered in K 6.0 and issues discovered during the development stages of K 6.0.
Question [Topic closed by moderator due to lack of interest] Not really sure what's wrong....
I have Joomla 1.5.15 and Kunena 1.5.8. The only mod for Kunena I have is udde IM.
Here's a screenshot of what's going on.
I would also take out every customised hack or modification that you have made. The simplest approach is to re-install K 1.5.9 over what you've now got.
Lastly, use the default_ex template without any modifications.
This combination should work ... at least it will establish that you were using something different. Does that sound reasonable to you?
As always, you should have a backup of your website as well as a test site where you can experiment before making any changes to your live, production site.
One of the best features about Kunena is that people can make lots of changes to it. One of the worst features about Kunena is that people do make lots of changes to it. :pinch:
In the first enable the debug mode in joomla configuration panel to see more detailled errors, this kind of errors come from to an error into a sql query, with this kind of error message is hard to diagnotize.
I don't provide support by PM, because this can be useful for someone else.
I have had this problem for some time and have posted before but no solution has been found.
The only workaround I found that works is to start pruning messages from your forum categories. Not ideal but start from say 90 days and work down 1 day at a time (90,89,88 etc) and keep reloading the page to see if its ok.
Eventually it the page reloads ok.
Like I said, no one including on here knows what causes it but the Pruning workaround will get it back up and running. Not ideal I know
Paul - www.hounslowtw3.net
Don't want to keep pruning the posts so turned on the debug and got the message in the attached post. I'm not a mysql expert so would appreciate any help.