- Posts: 21
- Thank you received: 0
Kunena 5.1.13 Released (21 Jul 2019)
The Kunena team has announce the arrival of Kunena 5.1.13 [K 5.1.13] which is now available for download as a native Joomla extension for J! 3.9.x. This version addresses most of the issues that were discovered in K 5.1 and issues discovered during the development stages of K 5.1.
Question Error 1054 Unknown column 'id'
i got a Problem with my Kunena.
First i updated Joomla from 1.5 to 3.6 with SP Upgrade 4.0.6.
Than install the new Kunena on new Site with new Joomla, Transfered User and all Stuf from old Joomla.
Than Transfered Old Kunena User, Posts, Topic etc. to new Kunena.
When i go to components ---> Kunena than comes a Error:
1054 Unknown column 'id' in 'where clause' SQL=SELECT * FROM #__kunena_configuration WHERE id=1
Any idea how to solve this Problem? Please help.
Please add this code on your database, and change the yourprefix with your own prefix:
CREATE TABLE IF NOT EXISTS `yourprefix_kunena_configuration` ( `id` int(11) NOT NULL default '0', `params` text NULL, PRIMARY KEY (id) ) DEFAULT CHARACTER SET utf8;
So i go to phpMyAdmin.
inside the Database.
At the header i click on the Tab "SQL".
i see a empty field. so copy and paste
CREATE TABLE IF NOT EXISTS `tg09a_kunena_configuration` (
`id` int(11) NOT NULL default '0',
`params` text NULL,
PRIMARY KEY (id) ) DEFAULT CHARACTER SET utf8;
Than click on ok.
than i see green field with text in german: MySQL lieferte ein leeres Resultat zurück, means like MySQL gave back an empty result
i go back to joomla backend, reload the site and go to Components --> Kunena Forum = nothin happen. same problem with the error text.
Then remove all kunena tables, then export the kunena tables from your J1.5
Then import it into you new database, check the tables if they have the correct prefix. Then install kunena package by the joomla installer.
Unfortunately, I have another problem: After migrating the categories to the new kunena 4, the categories list is empty, although the database has exactly the same content as the old database (frontend and backend). Is there a solution for this problem?
Oddly, the thrash bin in the new version has the same content than the old thrash bin, which I have not deleted.
- Not Allowed: to create new topic.
- Not Allowed: to reply.
- Not Allowed: to edit your message.