- Posts: 90
- Thank you received: 9
Kunena 7.0.2 Released
The Kunena team has announce the arrival of Kunena 7.0.2 [K 7.0.2] in stable which is now available for download as a native Joomla extension for J! 5.3.x/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
Solved Column twitter not renamed to x_social when upgrading to 6.3.2
1 year 9 months ago #231580
by Goldie
Hi,
this morning I upgraded to 6.3.2 and then I got a user complaint that he cannot save his signature in profile.
Error message was about field list x_social not being present.
I tracked it down to the fact that column twitter in Table __kunena_users was not renamed to x_social
MYSQL> ALTER TABLE __kunena_users RENAME COLUMN twitter TO x_social;
solved the issue. So there something got forgotten in sql upgrade from 6.3.1 to 6.3.2
this morning I upgraded to 6.3.2 and then I got a user complaint that he cannot save his signature in profile.
Error message was about field list x_social not being present.
I tracked it down to the fact that column twitter in Table __kunena_users was not renamed to x_social
MYSQL> ALTER TABLE __kunena_users RENAME COLUMN twitter TO x_social;
solved the issue. So there something got forgotten in sql upgrade from 6.3.1 to 6.3.2
The following user(s) said Thank You: rich
Please Log in or Create an account to join the conversation.
1 year 9 months ago #231609
by rich
Important! Always create a backup before you make any changes to your website!
Replied by rich on topic Column twitter not renamed to x_social when upgrading to 6.3.2
The column should actually be adjusted automatically during an upgrade, as the upgrade.xml contains the following command:
ALTER TABLE `#__kunena_users` CHANGE `twitter` `x_social` VARCHAR(75) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci NULL DEFAULT NULL;
I don't know why it doesn't work.
ALTER TABLE `#__kunena_users` CHANGE `twitter` `x_social` VARCHAR(75) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci NULL DEFAULT NULL;
I don't know why it doesn't work.
Important! Always create a backup before you make any changes to your website!
Please Log in or Create an account to join the conversation.
1 year 9 months ago #231618
by Goldie
Replied by Goldie on topic Column twitter not renamed to x_social when upgrading to 6.3.2
Hi rich,
I cannot tell either. I used that statement also now to bring x_social to VARCHAR(75) and it worked also in MariaDB. During 3 upgrades it did not work. What has worked was rename of Column bsky_app. That seems to have been missing before.
I cannot tell either. I used that statement also now to bring x_social to VARCHAR(75) and it worked also in MariaDB. During 3 upgrades it did not work. What has worked was rename of Column bsky_app. That seems to have been missing before.
Please Log in or Create an account to join the conversation.
Less
More
- Posts: 973
- Thank you received: 153
1 year 9 months ago - 1 year 9 months ago #231619
by Pinkeltje
Replied by Pinkeltje on topic Column twitter not renamed to x_social when upgrading to 6.3.2
Last edit: 1 year 9 months ago by Pinkeltje.
Please Log in or Create an account to join the conversation.
1 year 9 months ago #231623
by Goldie
Replied by Goldie on topic Column twitter not renamed to x_social when upgrading to 6.3.2
Hi rich,
could it be the version date that creates this failure? Same version for bsky_app and x_social but different versiondate .
could it be the version date that creates this failure? Same version for bsky_app and x_social but different versiondate .
Please Log in or Create an account to join the conversation.
1 year 9 months ago #231629
by rich
Important! Always create a backup before you make any changes to your website!
Replied by rich on topic Column twitter not renamed to x_social when upgrading to 6.3.2
I have tested it, but it makes no difference. The other columns like bsky_app is also not updated anymore if they are not present.
But the upgrade.xml is loaded, because if I intentionally insert an error, I get a message that the database cannot be updated.
It seems, the commands are no longer executed.
But the upgrade.xml is loaded, because if I intentionally insert an error, I get a message that the database cannot be updated.
It seems, the commands are no longer executed.
Important! Always create a backup before you make any changes to your website!
The following user(s) said Thank You: Gindi
Please Log in or Create an account to join the conversation.
Time to create page: 0.328 seconds