Question From Kunena 6.3.10 straight to Kunena 6.4.3

chris87 wrote:

Hi,
should have know earlier that I can potentially modify also the 6.4.3 DB with your query from above.
I have already set everything back to 6.3.10 (Joomla 5.3.1) status - my last version is line 43 now.
Can you please tell me what I should query now in the 6.3.10 DB in order to modify the DB prior to the 6.4.3 update?

Thank you.

Chris



 

The things had described before was to apply on a failed attempt to update to Kunena 6.4.3, it's not to be applied on Kunena 6.3.10.

To avoid to block your live site, is-it make to make a clone of your live site on a sub domain to testing purpose ?

Pinkeltje wrote:

can-you check in your table #__kunena_users if you have still the column delicious ?

Now it's too late he has reverted to Kunena 6.3.10

He already had this problem in 6.3.10

I was also not able to fix in Kunena 6.3 the twitter conversion to x_social, because the download of the patch was not accessible anymore.

So that is why I asked for a screenshot of users table to check.

The Kunena backend shows still 6.3.10 2025-03-14, but Joomla shows 6.4.3 installed.
I have deleted line 45 and 44 in the DB.
In my DB I have still the columns delicious, iqc, twitter, qqsocial and the newly added socials from above.

Maybe you have an approach for this?
Should I apply this as well?
ALTER TABLE `#__kunena_users` DROP `friendfeed`;
ALTER TABLE `#__kunena_users` ADD `bsky_app` varchar(75) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci NULL AFTER `reddit`;
ALTER TABLE `#__kunena_users` CHANGE `twitter` `x_social` VARCHAR(75) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci NULL DEFAULT NULL;
ALTER TABLE `#__kunena_users` DROP `icq`;
 

Apply the one to remove icq column

Now apply that queries in phpmyadmin to see if it's works on your install :

 

Thanks. To summarize I do the following in a K6.3.10 DB prior the to K6.4.3 update in Joomla 5.3.1:

ALTER TABLE `#__kunena_users` DROP `friendfeed`;
ALTER TABLE `#__kunena_users` ADD `bsky_app` varchar(75) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci NULL AFTER `reddit`;
ALTER TABLE `#__kunena_users` CHANGE `twitter` `x_social` VARCHAR(75) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci NULL DEFAULT NULL;
ALTER TABLE `#__kunena_users` DROP `icq`;

ALTER TABLE `#__kunena_users` ADD `socials` TEXT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci NULL AFTER `ip`;
ALTER TABLE `#__kunena_users` DROP `delicious`;
ALTER TABLE `#__kunena_users` CHANGE `bsky_app` `bluesky_app` VARCHAR(75) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci NULL DEFAULT NULL;
ALTER TABLE `#__kunena_users` DROP `socialshare`;

Is that a correct summary?

Chris
 

Not totally, don't apply the queries crossed out because it belongs to the K6.3.x updates steps not K6.4.x :

chris87 wrote:

Thanks. To summarize I do the following in a K6.3.10 DB prior the to K6.4.3 update in Joomla 5.3.1:

ALTER TABLE `#__kunena_users` DROP `friendfeed`;
ALTER TABLE `#__kunena_users` ADD `bsky_app` varchar(75) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci NULL AFTER `reddit`;
ALTER TABLE `#__kunena_users` CHANGE `twitter` `x_social` VARCHAR(75) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci NULL DEFAULT NULL;
ALTER TABLE `#__kunena_users` DROP `icq`;

ALTER TABLE `#__kunena_users` ADD `socials` TEXT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci NULL AFTER `ip`;
ALTER TABLE `#__kunena_users` DROP `delicious`;
ALTER TABLE `#__kunena_users` CHANGE `bsky_app` `bluesky_app` VARCHAR(75) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci NULL DEFAULT NULL;
ALTER TABLE `#__kunena_users` DROP `socialshare`;

Is that a correct summary?

Chris




 

Apply this query if you want to re-try to launch the install of K6.4.3 :