- Posts: 140
- Thank you received: 7
Kunena 6.3.0 released
The Kunena team has announce the arrival of Kunena 6.3.0 [K 6.3.0] in stable which is now available for download as a native Joomla extension for J! 4.4.x/5.0.x/5.1.x. This version addresses most of the issues that were discovered in K 6.2 and issues discovered during the last development stages of K 6.3
Question Kunena Internal Error - "500 - JDatabaseMySQL::query: 1104"
@fxstein: pls pm me the answer in german cause my english is still not good enough for those specific things
Please Log in or Create an account to join the conversation.
"Our settings in MySQL are done to strike a balance between allowing maximum functionality for customers and their databases and preserving resources to ensure that all customers enjoy unimpeded access to the server. We cannot change these settings globally, but if this cannot be added into the query somewhere, then I suspect this forum will not able to be used on our shared hosting."
Please Log in or Create an account to join the conversation.
Blue Eagle vs. Crypsis reference guide
Read my blog and
Please Log in or Create an account to join the conversation.
I accept the Kunena team won't change the code but can I test hacking it by adding the SET SQL_MAX_JOIN_SIZE=# statement somewhere?
Would anyone be so kind to say where that somewhere should be?
Cheers!
Paul
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
Can-you put the result of SHOW VARIABLES LIKE 'max_join_size'; in phpmyadmin ?
You can set SET SQL_BIG_SELECTS=1, just before the annoying query to see if it's works better...
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.
The result of SHOW VARIABLES LIKE 'max_join_size'; was
max_join_size = 900000
When you refer to "annoying query" above, what do you mean?
Rgds
Paul
Please Log in or Create an account to join the conversation.
This setting already allows for 900,000 records in a single join. Do you have more than 900,000 posts/topics?
This might indeed be a corrupted database. When did you first start using Kunena or Fireboard? What was the first version?
We love stars on the Joomla Extension Directory .
Please Log in or Create an account to join the conversation.
You definitely should consider dedicated hosting for the type of site you are running. Shared hosting is ok for a low volume personal blog, but never for an online community site. JomSocial and Kunena will almost never get enough resources on such a limited hosting plan.
You have less than 100 posts yet some of the pages take 4-5 seconds to build by the server. A sign that you run on a very oversubscribed shared hosting service.
Last but not least please make also sure you have 1.6.1 installed (can't tell).
We love stars on the Joomla Extension Directory .
Please Log in or Create an account to join the conversation.
Yes I am using Kunena 1.6.1 and I first started on Fireboard (1.0.5RC2) and then upgraded to Kunena. How would I fix a corrupted database?
Please Log in or Create an account to join the conversation.