Kunena 7.0.11 & Kunena 6.4.16 – Security Updates Released and K7.1 in RC1 2

The Kunena team has announce the arrival of three simultaneous security release : K6.4.16, K7.0.11 and K7.1 RC2. Just a reminder K6.4.16 receives only securities fixes untill end of 2026, so it's advised for users to upgrade to K7.0.11. K7.0.11 is the last release of the K7.0 because it's replaced by K7.1 branch with the stable release in the corner. The translations for K7.1 on crowdin.com/project/kunena-forum-7-1 needs to be checked or improved becasue it has been generated by TM (Translation Machine).

Solved Column twitter not renamed to x_social when upgrading to 6.3.2

More
2 years 4 months ago #231580 by Goldie
Column twitter not renamed to x_social when upgrading to 6.3.2 was created 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
 
The following user(s) said Thank You: rich

Please Log in or Create an account to join the conversation.

More
2 years 4 months ago #231609 by rich
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.
Important! Always create a backup before you make any changes to your website!

Please Log in or Create an account to join the conversation.

More
2 years 4 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.

Please Log in or Create an account to join the conversation.

More
2 years 4 months ago - 2 years 4 months ago #231619 by Pinkeltje
Replied by Pinkeltje on topic Column twitter not renamed to x_social when upgrading to 6.3.2
I don't know why it doesn't work either bur fact is that it doesn't work. I updated to Kunena 6.3.2, 2 days ago and after update I opened Kunena Dashboard.
Results:
Database

 

Action log

 
Last edit: 2 years 4 months ago by Pinkeltje.

Please Log in or Create an account to join the conversation.

More
2 years 4 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 .

Please Log in or Create an account to join the conversation.

More
2 years 4 months ago #231629 by rich
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.
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.141 seconds