- Posts: 16
- Thank you received: 2
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
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.
Question Upgrade from K2.0 to K.2.0.1 SQL failed
- NickJWStone
-
Topic Author
- Offline
- Junior Member
- NickJWStone
-
Topic Author
- Offline
- Junior Member
- NickJWStone
-
Topic Author
- Offline
- Junior Member
11 years 9 months ago #25
by NickJWStone
Replied by NickJWStone on topic Upgrade from K2.0 to K.2.0.1 SQL failed
I disabled the plugins. I was not aware these where activated, as I don't use both at all.
The forum is working now, except for the old Poll. Didn't test all features at the moment.
Thanks for your quick support!
The forum is working now, except for the old Poll. Didn't test all features at the moment.
Thanks for your quick support!
Please Log in or Create an account to join the conversation.
- NickJWStone
-
Topic Author
- Offline
- Junior Member
11 years 9 months ago #28
by Matias
Replied by Matias on topic Upgrade from K2.0 to K.2.0.1 SQL failed
Thank you for sharing your story. We've tried our best to make everything as stable as possible, but as always, it looks like we still have some unintended issues coming from migrations to the new versions. I hope that this will be the last total rewrite we need to do and in the future the changes will be smaller and more frequent (thus making them more robust).
JavaScript issue was coming from a bug we had with the old templates and we later found out that you just needed to change your template after installation in order to fix it. That bug has been fixed since then, so it doesn't affect upgrades from K1.7.
Avatar issue is something that I need to fix -- can you enable integrations one by one if some of the integrations is broken in your environment (ignore gravatars, though)? Just remember to turn off the plugins after test.
What comes to SQL issue, I would love to find a reliable way to reproduce it. So yes, if you were kind enough to setup your backup and play with it a bit, it would be great help for the other users in the future.
JavaScript issue was coming from a bug we had with the old templates and we later found out that you just needed to change your template after installation in order to fix it. That bug has been fixed since then, so it doesn't affect upgrades from K1.7.
Avatar issue is something that I need to fix -- can you enable integrations one by one if some of the integrations is broken in your environment (ignore gravatars, though)? Just remember to turn off the plugins after test.
What comes to SQL issue, I would love to find a reliable way to reproduce it. So yes, if you were kind enough to setup your backup and play with it a bit, it would be great help for the other users in the future.
Please Log in or Create an account to join the conversation.
11 years 6 months ago #29
by senes
Replied by senes on topic Upgrade from K2.0 to K.2.0.1 SQL failed
Had the same problem.
How I solved this:
-> Deleted firstly all entries in kunena_poll_users to finish the installation.
-> Took kunena_poll_users from the backup.
-> Use a script which should make the same as
UPDATE #__kunena_polls_users AS a INNER JOIN #__kunena_topics AS t ON t.id=a.pollid LEFT JOIN #__kunena_polls AS p ON p.id=a.pollid SET a.pollid=t.poll_id WHERE t.poll_id>0 AND p.id IS NULL
and convert the table.
My code snippet:
After you have done this, there can be (like on my table) rows which have not been changed, these had a pollid > max(#__kunena_polls.id).
I checked the pollid of this in kunena_topics, but there were no entries. That means, this are entries of deleted topics, so I just used the following query to delete them:
It's a little unprofessional but it should work, hope there is no mistake in my thinking.
Hope it helps you
Yours sincerely
How I solved this:
-> Deleted firstly all entries in kunena_poll_users to finish the installation.
-> Took kunena_poll_users from the backup.
-> Use a script which should make the same as
UPDATE #__kunena_polls_users AS a INNER JOIN #__kunena_topics AS t ON t.id=a.pollid LEFT JOIN #__kunena_polls AS p ON p.id=a.pollid SET a.pollid=t.poll_id WHERE t.poll_id>0 AND p.id IS NULL
and convert the table.
My code snippet:
Code:
$polls = query("SELECT t.id,u.pollid,t.poll_id,t.subject ".
"FROM #__kunena_polls_users u, #__kunena_topics t ".
"WHERE t.id = u.pollid ".
"GROUP BY t.id ".
"ORDER BY t.poll_id");
foreach($polls as $poll){
echo execute("UPDATE #__kunena_polls_users SET u.pollid=".$poll->poll_id." WHERE pollid=".$poll->pollid);
}
After you have done this, there can be (like on my table) rows which have not been changed, these had a pollid > max(#__kunena_polls.id).
I checked the pollid of this in kunena_topics, but there were no entries. That means, this are entries of deleted topics, so I just used the following query to delete them:
Code:
DELETE FROM `#__kunena_polls_users` WHERE pollid > [insert max(#__kunena_polls.id) here.]
It's a little unprofessional but it should work, hope there is no mistake in my thinking.
Hope it helps you
Yours sincerely
Please Log in or Create an account to join the conversation.
Time to create page: 0.571 seconds