Solved SQL syntax

Hi
I am Delighted that you are taking an interest in this for me.
You want to know, now, is exactly where and what causes this syntax error to appear. Can you help us please to write the exact procedure

This is the WHOLE procedure and you will need to know a little of the back story.
The aim was to take one site (Know as ORG) from Joomla 1-5 to Joomla 2-5.
The idea as to use two domains as moving my large site would cause problems.
I hired a company and they used the SP Upgrade to copy - migrate ORG to another site on the same server (INFO)

The site as been up since 2007 so there was a lot to migrate.
Community Builder, JReviews, Jevents, Joomgallery, uddeIM, Kunena 1-7, plus 200 site modules & plug-ins.

Not everything worked, Community Builder had permissions errors, JReviews I had to set up Categories, Jevents lost data, Joomgallery, didn’t link to the images, the most import one was Kunena which had " registered " - "administrators" errors.

Work started on INFO to fix the errors, Jevents & Joomgallery, it was easier to start again, support at JReview helped and sorted their component, Community Builder was OK.
All the new versions of the old site components - modules were added, Listbingo, DJ Classifieds, plus some new components - modules. The only one that was in error was the Kunena " registered " - "administrators" issue

Then one day I was following the “” ‘SOLVED ISSUE’ instructions on the Kunena forum = with one click solution. Deny privileges to edit the component.””.
>>> LINK <<<

After loging out and back in the admin menu had disappeared, so I asked on the Joomla forum but they were unable to help.
>>> LINK <<<

So I uploaded a fresh copy of Joomla 2-5 to yet another site ( DATE ), and I transferred the files-folders via FTP and I just kept adding data tables until I had a mirror version of the site.
It was strange that the Kunena " registered " - "administrators" issue didn't happen when I did it this way.
Once I got the second site fully working (back & front ends) (DATE) I copied over the second site tables to the broken site. (INFO).

So now I have TWO fully working sites (INFO) + (DATE) all the forum postings are there, every is fine, these are now updated from Kunena 1-7 to Kunena 2-1.
Of course this was taken time, about 3 weeks, so members, forum and uddeIM need updating from ORG.

The plan took place overnight and was to copy- migrate just some of the data tables from ORG to INFO using SP Upgrade, userport and J2XML Importer.

This was done by a very good website developer and after EVERYTHING was double checked on INFO then he used XCloner to take INFO and put it on ORG.

While he was doing that I moved the ORG J 1-5 to yet another site (NET) as a back up.

Everything was fine, ORG J2-5 was working, INFO J2-5 was working, NET J1-5 was working

But when I upgraded Kunena 2-1, to Kunena 2-2 that’s when the problems started.
I found that Kunena 2-2 would not work fully on NET J1-5 although the server sites are all set up the same but this only discovered AFTER the upgrade.

I have since found this SQL syntax error is on every site, but who checks ‘Trash Manger topics’ for errors when you have no trash to check !!

Since the upgrade to Kunena 2-2 on ORG and INFO the amount of text in each posting has disappeared which means that I have to check and edit some 22992 forum messages and copy them from DATE which did update OK.




I short; IF I had stayed with Kunena 1-7 or Kunena 2-1 then maybe I could have lived with it

So the way to reproduce this problem is to use the Kunena Trash Manager on a forum that has many messages but no deleted (trashed) posts. Is that a fair summary of the way to reproduce this problem?

My question is this: irrespective of whether you use the Kunena Trash Manager (with or without trashed posts) can you

(a) use all the other backend features of Kunena; and
(b) are there issues on the frontend of your website?

Hi
yeah if you search in the Kunena Trash Manager TOPICS you may get this


As far as I know all the other stuff is working on the back and front except the front end REVIEW of postings and text sizes but that maybe a script conflict.



Cheers

Hello,

To fix the issue, open /administrator/components/com_kunena/models/trash.php and replace line 146 :

by

Hi


That has fixed the SQL syntax error in the Kunena Trash Manager.


Thanks