Kunena 6.2.1 Released with module latest 6.0.4 and module kunena stats 6.0.4

The Kunena team has announce the arrival of Kunena 6.2.1 [K 6.2.1] which is now available for download as a native Joomla extension for J! 4.3.x/4.4.x/5.0.x. This version addresses most of the issues that were discovered in K 6.1.0 and issues discovered during the last development stages of K 6.1

Topics must relate to a currently supported version of Kunena. If you are unsure what is the current supported version of Kunena, please go to the download page.

If you are having problems then, for your own benefit, it would save us all a lot of time if you would kindly post your configuration report when you ask for help from this forum. If you do not post your configuration report we will not ask you for it but you will probably not get your problem solved, either.

Question Warning about Kunena extensions before update Joomla to 4.4.

More
4 weeks 1 hour ago #1 by lemur
I use Joomla 4.3.4 and want to upgrade to Joomla  4.4.
Before updating, Joomla checks extensions and issues warnings about the inconsistency of some applications.
Among these were several applications of Kunena.

Third-party Extension Checks
Update information not available
Joomla cannot detect the compatibility of the extension with the target version of Joomla. Extension Name Extension Type

Kunena Language Package
Content - Kunena Discussion Plugin
Kunena News Module
KunenaSearch

At the same time, I have the latest version Kunena installed, including these applications.

Why are these apps shown in the list?
Do I need to pay attention to this warning, or can I run the update to Joomla 4.4.?

Thanks

This message contains confidential information

Database collation check: j3d_kunena_aliases have wrong collation of type utf8mb3_unicode_ci on field type  j3d_kunena_aliases have wrong collation of type utf8mb3_unicode_ci on field item  j3d_kunena_announcement have wrong collation of type utf8mb3_unicode_ci on field title  j3d_kunena_announcement have wrong collation of type utf8mb3_unicode_ci on field sdescription  j3d_kunena_announcement have wrong collation of type utf8mb3_unicode_ci on field description  j3d_kunena_attachments have wrong collation of type utf8mb3_unicode_ci on field hash  j3d_kunena_categories have wrong collation of type utf8mb3_unicode_ci on field name  j3d_kunena_categories have wrong collation of type utf8mb3_unicode_ci on field icon  j3d_kunena_categories have wrong collation of type utf8mb3_unicode_ci on field accesstype  j3d_kunena_categories have wrong collation of type utf8mb3_unicode_ci on field channels  j3d_kunena_categories have wrong collation of type utf8mb3_unicode_ci on field description  j3d_kunena_categories have wrong collation of type utf8mb3_unicode_ci on field headerdesc  j3d_kunena_categories have wrong collation of type utf8mb3_unicode_ci on field class_sfx  j3d_kunena_categories have wrong collation of type utf8mb3_unicode_ci on field params  j3d_kunena_configuration have wrong collation of type utf8mb3_unicode_ci on field params  j3d_kunena_messages have wrong collation of type utf8mb3_unicode_ci on field name  j3d_kunena_messages have wrong collation of type utf8mb3_unicode_ci on field email  j3d_kunena_messages have wrong collation of type utf8mb3_unicode_ci on field subject  j3d_kunena_messages have wrong collation of type utf8mb3_unicode_ci on field ip  j3d_kunena_messages have wrong collation of type utf8mb3_unicode_ci on field modified_reason  j3d_kunena_polls_options have wrong collation of type utf8mb3_unicode_ci on field text  j3d_kunena_sessions have wrong collation of type utf8mb3_unicode_ci on field allowed  j3d_kunena_sessions have wrong collation of type utf8mb3_unicode_ci on field readtopics  j3d_kunena_smileys have wrong collation of type utf8mb3_unicode_ci on field code  j3d_kunena_smileys have wrong collation of type utf8mb3_unicode_ci on field location  j3d_kunena_smileys have wrong collation of type utf8mb3_unicode_ci on field greylocation  j3d_kunena_topics have wrong collation of type utf8mb3_unicode_ci on field subject  j3d_kunena_topics have wrong collation of type utf8mb3_unicode_ci on field first_post_message  j3d_kunena_topics have wrong collation of type utf8mb3_unicode_ci on field first_post_guest_name  j3d_kunena_topics have wrong collation of type utf8mb3_unicode_ci on field last_post_message  j3d_kunena_topics have wrong collation of type utf8mb3_unicode_ci on field last_post_guest_name  j3d_kunena_topics have wrong collation of type utf8mb3_unicode_ci on field params  j3d_kunena_users have wrong collation of type utf8mb3_unicode_ci on field view  j3d_kunena_users have wrong collation of type utf8mb3_unicode_ci on field signature  j3d_kunena_users have wrong collation of type utf8mb3_unicode_ci on field personalText  j3d_kunena_users have wrong collation of type utf8mb3_unicode_ci on field location  j3d_kunena_users have wrong collation of type utf8mb3_unicode_ci on field icq  j3d_kunena_users have wrong collation of type utf8mb3_unicode_ci on field yim  j3d_kunena_users have wrong collation of type utf8mb3_unicode_ci on field skype  j3d_kunena_users have wrong collation of type utf8mb3_unicode_ci on field twitter  j3d_kunena_users have wrong collation of type utf8mb3_unicode_ci on field facebook  j3d_kunena_users have wrong collation of type utf8mb3_unicode_ci on field myspace  j3d_kunena_users have wrong collation of type utf8mb3_unicode_ci on field linkedin  j3d_kunena_users have wrong collation of type utf8mb3_unicode_ci on field delicious  j3d_kunena_users have wrong collation of type utf8mb3_unicode_ci on field friendfeed  j3d_kunena_users have wrong collation of type utf8mb3_unicode_ci on field digg  j3d_kunena_users have wrong collation of type utf8mb3_unicode_ci on field blogspot  j3d_kunena_users have wrong collation of type utf8mb3_unicode_ci on field flickr  j3d_kunena_users have wrong collation of type utf8mb3_unicode_ci on field bebo  j3d_kunena_users have wrong collation of type utf8mb3_unicode_ci on field websitename  j3d_kunena_users have wrong collation of type utf8mb3_unicode_ci on field websiteurl  j3d_kunena_users_banned have wrong collation of type utf8mb3_unicode_ci on field ip  j3d_kunena_users_banned have wrong collation of type utf8mb3_unicode_ci on field reason_private  j3d_kunena_users_banned have wrong collation of type utf8mb3_unicode_ci on field reason_public  j3d_kunena_users_banned have wrong collation of type utf8mb3_unicode_ci on field comments  j3d_kunena_users_banned have wrong collation of type utf8mb3_unicode_ci on field params  j3d_kunena_version have wrong collation of type utf8mb3_unicode_ci on field version  j3d_kunena_version have wrong collation of type utf8mb3_unicode_ci on field versionname  j3d_kunena_version have wrong collation of type utf8mb3_unicode_ci on field state  
        

Joomla! SEF: Enabled | Joomla! SEF rewrite: Disabled | FTP layer: Disabled |
        

This message contains confidential information
htaccess: Exists | PHP environment: Max execution time: 30 seconds | Max execution memory: 256M | Max file upload:  

Kunena menu details:

Warning: Spoiler!

Joomla default template details : purity_III | author: JoomlArt.com | version: 2.1.0 | creationdate: Nov 10th, 2023

Kunena default template details : Aurelia | author: Kunena Team | version: 6.2.0 | creationdate: 2023-10-17

Kunena template params:

Warning: Spoiler!

Kunena version detailed: Kunena 6.2.0 | 2023-10-17 [ Git Repository ]
        | Kunena detailed configuration:

Warning: Spoiler!
| Kunena integration settings:
Warning: Spoiler!
| Joomla! detailed language files installed:
Warning: Spoiler!

Third-party components: CommunityBuilder 2.9.0

Third-party SEF components: None

Plugins: Content - Kunena Discuss 6.0.3

Modules: Kunena Latest 6.0.3 | Kunena Search 6.0.3


- - - - - - - - -
Signature:
Many thanks to Rich and the other advisors.

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

More
3 weeks 6 days ago #2 by rich
Nothing should actually happen. But to be on the safe side, you can disable this extension during the upgrade.
But it is important that a backup is created before each installation or upgrade.
The following user(s) said Thank You: lemur

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

More
3 weeks 6 days ago #3 by lemur
Thank you.

Sorry for being offtopic, but I (first) noticed in Confidential information that I have a problem with collation in Kunena tables.

About all tables are reported: 

_kunena_categories have wrong collation of type utf8mb3_unicode_ci on field name
_kunena_categories have wrong collation of type utf8mb3_unicode_ci on field icon
_kunena_categories have wrong collation of type utf8mb3_unicode_ci on field accesstype


and so on.

Table check diagnostics in Kunena do not show this problem.

Does this interfere with Kunena's work?
Is it dangerous?
Do I need to convert all fields of all tables to, for example, utf8mb4_unicode_ci? Or to another collation?

Thank you

- - - - - - - - -
Signature:
Many thanks to Rich and the other advisors.

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

More
3 weeks 5 days ago #4 by rich
I am surprised that the collation is not correct after you have already installed Kunena 6.2. This should be adjusted automatically during an upgrade when you go to the dashboard afterwards.
The tables and columns should be converted to utf8mb4, which is also Joomla standard.

Does this interfere with Kunena's work?

utf8mb4-based collations are much faster

Is it dangerous?

No

Do I need to convert all fields of all tables to, for example, utf8mb4_unicode_ci? Or to another collation?

Table and colums should be the same collation.

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

More
3 weeks 5 days ago #5 by lemur

I am surprised that the collation is not correct after you have already installed Kunena 6.2. This should be adjusted automatically during an upgrade when you go to the dashboard afterwards.
The tables and columns should be converted to utf8mb4, which is also Joomla standard.
...
Table and colums should be the same collation.

Thanks for the quick response.

If the tables were supposed to be converted to the new collation when installing Kunena 6.2 and this did not happen, then some minor bug was probably the cause.

Will this bug be fixed in future versions of Kunena?
Since this problem is not critical to the functioning of Kunena, I would wait for a fixed version.

Have a good Sunday.

- - - - - - - - -
Signature:
Many thanks to Rich and the other advisors.

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

More
3 weeks 4 days ago #6 by rich
I'm sorry, it was my mistake. I have spoken to the developer, Kunena converts only when it's in utf8_general_ci, utf8mb3_general_ci or utf8_unicode_ci, but you have collation utf8mb3_unicode_ci, so nothing was converted.
This will be added in one of the next versions. So you can wait until Kunena 6.2.2 or K 6.2.3 if you don't want to do it yourself.

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

More
3 weeks 2 days ago #7 by lemur

I'm sorry, it was my mistake. I have spoken to the developer, Kunena converts only when it's in utf8_general_ci, utf8mb3_general_ci or utf8_unicode_ci, but you have collation utf8mb3_unicode_ci, so nothing was converted.
This will be added in one of the next versions. So you can wait until Kunena 6.2.2 or K 6.2.3 if you don't want to do it yourself.

Thank you very much!

- - - - - - - - -
Signature:
Many thanks to Rich and the other advisors.

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

Time to create page: 0.386 seconds