- Posts: 9
- Thank you received: 0
×
Kunena 5.2 Beta 1 Released (24 Sep 2020)
The Kunena team is thrilled to announce the first public beta release of Kunena 5.2, a native Joomla extension for Joomla 3.9. This is a development release and should be only be used for testing; this version is not recommended for live websites at this stage.
The purpose of this release is to encourage testing by downloading, installing and identifying any problems or shortcomings that people may discover. K 5.2.0 B1 is stable and we are aware that people will discover defects. We encourage you to use the forum to report defects, as soon as they are discovered, so that the development team can work through the problems before the release of K 5.1 as a stable product. Reporting defects does not mean that the problems can or will be fixed. The Kunena team is looking forward to hearing your feedback on how well we have achieved our design goals.
×
This is for users to help other users, to discuss topics that are related to forum administration in general or problems in running Joomla. This is not the place to ask for Joomla support. If you want assistance with Joomla please ask at
forum.joomla.org
Question J! 3.1.1 SQL errors in backend
7 years 2 months ago - 7 years 2 months ago #1
by johnoros
J! 3.1.1 SQL errors in backend was created by johnoros
Hello all,
Any help with the following issue much appreciated.
Receive the following error when login to administrator
SQL=SELECT * FROM `pre_updates` WHERE `extension_id` > 0 AND `detailsurl` LIKE ' update.kunena.org/% '
As a result you cannot access anything in the administrator without clicking on the username under logged in users. Here you see the users profile, click close and then you can access everything in the joomla administration.
There is no such table in the database _updates.
Alos Receive the following error in joomla 3.1.1 when trying to install joommsef Kunena extension.
SQL=SHOW FULL COLUMNS FROM `pre_updates`
Please see attachec image showing error in the joomla admin control panel after login
Any help with this sql issue much appreciated.
Thanks,
JohnO
Any help with the following issue much appreciated.
Receive the following error when login to administrator
SQL=SELECT * FROM `pre_updates` WHERE `extension_id` > 0 AND `detailsurl` LIKE ' update.kunena.org/% '
As a result you cannot access anything in the administrator without clicking on the username under logged in users. Here you see the users profile, click close and then you can access everything in the joomla administration.
There is no such table in the database _updates.
Alos Receive the following error in joomla 3.1.1 when trying to install joommsef Kunena extension.
SQL=SHOW FULL COLUMNS FROM `pre_updates`
Please see attachec image showing error in the joomla admin control panel after login
Any help with this sql issue much appreciated.
Thanks,
JohnO
Please Log in or Create an account to join the conversation.
7 years 2 months ago #4
by sozzled
Blue Eagle vs. Crypsis reference guide
Read my blog and
Replied by sozzled on topic J! 3.1.1 SQL errors in backend
Hmm ...
It's certainly possible to export K 2.0 tables from one site to another site (with K 2.0 installed) but copying K 2.0 tables from one site and hoping that they will work on a K 3.0 site? I don't think so.
Assuming that you were able to successfully migrate your J! 1.5 users from the old site and then copy the Joomla user tables from the migrated site to your new Joomla something-or-other site there are going to be issues with that.
It's certainly possible to export K 2.0 tables from one site to another site (with K 2.0 installed) but copying K 2.0 tables from one site and hoping that they will work on a K 3.0 site? I don't think so.
Assuming that you were able to successfully migrate your J! 1.5 users from the old site and then copy the Joomla user tables from the migrated site to your new Joomla something-or-other site there are going to be issues with that.
Blue Eagle vs. Crypsis reference guide
Read my blog and
Please Log in or Create an account to join the conversation.
7 years 2 months ago #6
by sozzled
Blue Eagle vs. Crypsis reference guide
Read my blog and
Replied by sozzled on topic J! 3.1.1 SQL errors in backend
You cannot copy a K 2.0 tables to a K 3.0 installation. Physically, you can copy them but there are differences in the table structure (not a lot of differences but one or two that break backward compatibility).
Best bet is to migrate in stages. Go from K 2.0.4 on J! 1.5 to K 2.0.4 on J! 2.5, then upgrade to K 3.0 on the J! 2.5 site and then copy the K 3.0 tables. That's just a suggestion and I can't guarantee that it will work.
I don't know anything about a _pre_updates table (which, as far as I'm aware, has nothing to do with Kunena). That sounds more like a Joomla issue to me. I could be wrong, of course. Does the Joomla forum have any information about this table?
Best bet is to migrate in stages. Go from K 2.0.4 on J! 1.5 to K 2.0.4 on J! 2.5, then upgrade to K 3.0 on the J! 2.5 site and then copy the K 3.0 tables. That's just a suggestion and I can't guarantee that it will work.
I don't know anything about a _pre_updates table (which, as far as I'm aware, has nothing to do with Kunena). That sounds more like a Joomla issue to me. I could be wrong, of course. Does the Joomla forum have any information about this table?
Blue Eagle vs. Crypsis reference guide
Read my blog and
Please Log in or Create an account to join the conversation.
7 years 2 months ago #8
by sozzled
Blue Eagle vs. Crypsis reference guide
Read my blog and
Replied by sozzled on topic J! 3.1.1 SQL errors in backend
Did you try cleaning the cache of the "Extension Manager: Update"?
Blue Eagle vs. Crypsis reference guide
Read my blog and
Please Log in or Create an account to join the conversation.
7 years 2 months ago #10
by sozzled
Blue Eagle vs. Crypsis reference guide
Read my blog and
Replied by sozzled on topic J! 3.1.1 SQL errors in backend
These are not Kunena issues. These are Joomla issues.
Blue Eagle vs. Crypsis reference guide
Read my blog and
Please Log in or Create an account to join the conversation.
Forum Access
- Not Allowed: to create new topic.
- Not Allowed: to reply.
- Not Allowed: to edit your message.
Time to create page: 0.284 seconds