×
Kunena 5.1.14 Released - Security release (13 Aug 2019)

The Kunena team is proud to announce the arrival of Kunena 5.1.14 [K5.1.14] which is now available for download as a native Joomla extension for Joomla 3.9.x. This version addresses most of the issues that were discovered in K 5.1 and issues discovered during the development stages of K 5.1.14. This update fixed 1 security issue.

× 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 Users cannot insert emoticons from mobile device keyboard

More
6 months 2 weeks ago #11 by rich
If you install Kunena new, it creates the tables with the collation which you have set as default in your database. If you want afterwards to change it, you must do it yourself.

What I need is advice on changing the encoding/collation of a column in an existing table.

Should work with phpMyAdmin (click on table -> Operations) but it will change it for all columns, and I've no idea whether is correct if you only for single table changes the collation.

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

More
6 months 2 weeks ago #12 by tcn

If you install Kunena new, it creates the tables with the collation which you have set as default in your database. If you want afterwards to change it, you must do it yourself.

I checked the defaults and they neither agree with the table collation nor with the encoding of the column in the table:

SELECT @@collation_server;
SELECT @@character_set_server;
 
latin1_swedish_ci
latin1
Moreover, is it wise to create tables with the default settings? The application knows best what it needs based on what it needs to support. So, shouldn't the tables and/or columns be created according to the needs of the application?

Should work with phpMyAdmin (click on table -> Operations) but it will change it for all columns, and I've no idea whether is correct if you only for single table changes the collation.

The thing is the collation setting for the table is correct. It's set to utf8mb4_unicode_ci. The column in the table, though, uses a different collation, namely utf8_general_ci. That's why local emotes cannot be inserted.

Should I rather open a bug in GitHub, so one of the developers can chime in and hopefully provide some insights?

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

More
6 months 2 weeks ago #13 by tcn
I read up on the subject a little more and found quite a good guide regarding what has to be done if one were to convert an entire database from utf8 to utf8mb4:

mathiasbynens.be/notes/mysql-utf8mb4

I don't think it's necessary to convert the entire Joomla database. However, converting columns other than of type text requires special attention as described in Step 4. I also took a look at which text columns of the Kunena tables are set to use utf8:

SELECT TABLE_NAME, COLUMN_NAME, CHARACTER_SET_NAME, COLLATION_NAME FROM `information_schema`.`COLUMNS` WHERE `COLLATION_NAME` = 'utf8_general_ci' AND `TABLE_NAME` LIKE '%kunena%' AND `DATA_TYPE` = 'text'
It's quite a few. But, again, not all of them need to support the full range of unicode characters. The candidates I came up with are, besides the messages, announcements and maybe user signatures.

But, as I mentioned before, I'd like to hear Kunena's position in this matter before embarking on this adventure.

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

More
6 months 2 weeks ago #14 by rich

Illegal mix of collations (utf8_general_ci,IMPLICIT) and (utf8mb4_general_ci,COERCIBLE) for operation '='

hm.. this problem seems not unknown. Please enter the error message (quote above) in the google search. You get many hits.

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

More
6 months 2 weeks ago #15 by tcn
Meanwhile the cause of the problem has been determined (thanks Slacker) and a possible solution found. What I'd still like to know:
  • Does Kunena support inserting emotes (and other special characters) directly into messages?
  • If so, why are the tables/columns not configured using the correct collation?
  • If so, will this be addressed in a future update (i.e. changing the collation)?
  • If not, will the error message be changed, so it doesn't look like a misconfiguration?
  • What's the developers point of view on this? Do they consider it a bug, a feature request or something else?

I'm asking all these questions, since I'm hesitant making changes to the database. In my opinion the Kunena tables belong to Kunena and should be maintained by Kunena. I could imagine that less tech savvy users would be at a complete loss as how to resolve the issue. They could potentially even shoot themselves in the foot.

For similar reasons, I have also restrained myself from making changes to the Kunena code. I know I could. But I also know it will come back to haunt me or my successor. Upstream is where changes should be made.

I read through issue #3805 , where this has been brought up before. But it remains unclear if any action has been taken back then like suggested in the last comment.

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

More
1 week 4 days ago - 1 week 4 days ago #16 by terminus
I have not migrated any data, started from scratch instead. But I have the same Problem with Emojis, when a user insert them from his cellphone.

Any Ideas?

Cheers
Last edit: 1 week 4 days ago by terminus.

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

  • Not Allowed: to create new topic.
  • Not Allowed: to reply.
  • Not Allowed: to edit your message.
Time to create page: 0.103 seconds