Question Testserver: update to K6.2 shows database error

When I update to Kunena 6.2.0 on my test server with Joomla 4.3.4 and Kunena 6.1.4, I get a database error in the sidepanel at System / Maintenance.

There are tables that are not up to date.
Kunena Forum has a problem:
The table "'jom4_kunena_ranks'" has the wrong type or attributes for the column "'rankTitle'" with type "varchar(255)". (From file: "6.0.0-BETA1-DEV.sql".)
    Table "'jom4_kunena_ranks'" has wrong type or attributes for column "'rankImage'" with type "varchar(255)". (From file: "6.0.0-BETA1-DEV.sql".)
        6.0.0-RC1-DEV 6.2.0 Unknown 262

When I use phpMyAdmin to view the xxxx_kunena_ranks table, "rankTitle" and "rankImage" says varchar(250) as the type is supposed to be varchar(255).
At "rankTitle" is also at zero yes and at standard NULL, should is at zero no and standard empty.
If I change "rankTitle" and "rankImage" to setpoint, the error is gone.

Addendum:
The database error is not yet present after the update, it only occurs when you click on Kunena in the Dashboard and the following messages are displayed in the Kunena Dashboard: "Database upgraded to version 6.2.0-DEV" and "Database upgraded to version 6.2.0-BETA3-DEV" and "Database upgraded to version 6.2.0-RC1-DEV".

Gindi
 

The database error remains even when updating from K6.2 to K6.2.1-DEV.

Gindi
 

I just dared to update the Lifesite from K6.1.4 to K6.2.0.
After accessing the Kunena forum, the error also occurs on the Lifesite.

Gindi

Gindi wrote:

When I update to Kunena 6.2.0 on my test server with Joomla 4.3.4 and Kunena 6.1.4, I get a database error in the sidepanel at System / Maintenance.

 

Hello,

This Joomla! feature doesn't handle the Kunena tables

Gindi wrote:

When I use phpMyAdmin to view the xxxx_kunena_ranks table, "rankTitle" and "rankImage" says varchar(250) as the type is supposed to be varchar(255).

Not now all the columns in VARCHAR(255) should be in VARCHAR(250) else it can't converted in ut8_mb4 with MySQL
 

Does this mean that everyone who uses MariaDB has to live with this bug?

Gindi

Hello,

I don't call it a bug, MariaDB and MySQL start to differ so the both works differently

In the code in Kunena which take care of conversion of columns to ut8_mb4 i can add a check so when you are using mysql and when the column is still in VARCHAR(255) it won't throw the error