Kunena 7.0.5 & Kunena 6.4.11 – Security Updates Released
The Kunena team has announce the arrival of Kunena 7.0.5 [K 7.0.5] 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 eleventh version of Kunena 6.4, a native Joomla extension for Joomla! 5.0, 5.1, 5.2, 5.3, 5.4 and 6.0.
Topics that are moved into this category are generally considered to be closed. Users may want to add additional information but these topics should not be resurrected in order to discuss new problems or unrelated matters.
Solved SQL syntax
13 years 7 months ago - 13 years 7 months ago #134461
by sozzled
Blue Eagle vs. Crypsis reference guide
Read my blog and
Replied by sozzled on topic SQL syntax
As you know, this is a community-run self-help forum. if, however, you are genuinely offering to pay someone to devote their time to assist you, I would be pleased to move this topic into a different category.
Looking at the way you have described your problem, I would say that your database has a record in the kunena_messages table without a corresponding / matching record in the kunena_messages_text table. Should be easy enough to delete the offending record from the database using phpMyAdmin or something similar. The problem lies in the database.
The problem could be exacerbated by the complicated Joomla menu arrangement shown in your configuration report, but that's not our problem, really. If your menu works, that's wonderful. If you keep having problems - and you seem to have a lot of problems on your sit - it may be worthwhile thinking about simplifying your menu.
Looking at the way you have described your problem, I would say that your database has a record in the kunena_messages table without a corresponding / matching record in the kunena_messages_text table. Should be easy enough to delete the offending record from the database using phpMyAdmin or something similar. The problem lies in the database.
The problem could be exacerbated by the complicated Joomla menu arrangement shown in your configuration report, but that's not our problem, really. If your menu works, that's wonderful. If you keep having problems - and you seem to have a lot of problems on your sit - it may be worthwhile thinking about simplifying your menu.
Blue Eagle vs. Crypsis reference guide
Read my blog and
Last edit: 13 years 7 months ago by sozzled.
Please Log in or Create an account to join the conversation.
13 years 7 months ago #134467
by sozzled
Blue Eagle vs. Crypsis reference guide
Read my blog and
Replied by sozzled on topic SQL syntax
*** Topic moved at user's request ***
Blue Eagle vs. Crypsis reference guide
Read my blog and
Please Log in or Create an account to join the conversation.
13 years 7 months ago - 13 years 7 months ago #134483
by sozzled
Blue Eagle vs. Crypsis reference guide
Read my blog and
Replied by sozzled on topic SQL syntax
I can tell you exactly where the syntax error occurs but what has me completely baffled is how this issue arises from the use of the Kunena Trash Manager.
The SQL syntax is wrong in
because it is missing a logical AND or OR operator between two parts of the WHERE clause. This would probably be more syntactically correct
But whether the correct syntax fixes the problem, I have no idea.
What I do not understand is how an SQL statement like this is generated using the Kunena Trash Manager. This kind of statement would seem more in appropriate in the context of using the Kunena search facility.
Clearly there is a bug in the way the SQL statement was formed but, before we can deal with this properly as a support matter, we need to know exactly, step by step, what you did to generate the error and how we may be able to reproduce the conditions either on your site or on a test site.
My earlier conclusion (that the problem lies in your database) was probably wrong. What is important to know, now, is exactly where and what causes this syntax error to appear. Can you help us please to write the exact procedure (perhaps with screenshots) that we can use to identify the cause of this SQL syntax error? Thank you.
I am moving this topic back to the K 2.0 Support category.
The SQL syntax is wrong in
Code:
SELECT COUNT(*) FROM jos2_kunena_topics AS tt WHERE tt.hold IN (2,3) AND tt.category_id IN (46,28,38,53,34,48,44,55,78,29,50,30,51,32,57,58,79,80) (tt.subject LIKE '%we%' OR tt.first_post_userid LIKE '%we%' OR tt.id LIKE '%we%') AND tt.moved_id='0'
Code:
SELECT COUNT(*) FROM jos2_kunena_topics AS tt WHERE tt.hold IN (2,3) AND tt.category_id IN (46,28,38,53,34,48,44,55,78,29,50,30,51,32,57,58,79,80) AND (tt.subject LIKE '%we%' OR tt.first_post_userid LIKE '%we%' OR tt.id LIKE '%we%') AND tt.moved_id='0'
What I do not understand is how an SQL statement like this is generated using the Kunena Trash Manager. This kind of statement would seem more in appropriate in the context of using the Kunena search facility.
Clearly there is a bug in the way the SQL statement was formed but, before we can deal with this properly as a support matter, we need to know exactly, step by step, what you did to generate the error and how we may be able to reproduce the conditions either on your site or on a test site.
My earlier conclusion (that the problem lies in your database) was probably wrong. What is important to know, now, is exactly where and what causes this syntax error to appear. Can you help us please to write the exact procedure (perhaps with screenshots) that we can use to identify the cause of this SQL syntax error? Thank you.
I am moving this topic back to the K 2.0 Support category.
Blue Eagle vs. Crypsis reference guide
Read my blog and
Last edit: 13 years 7 months ago by sozzled.
Please Log in or Create an account to join the conversation.
Time to create page: 0.295 seconds