Hi @kabbill21,
Thank you for reaching out.
I checked the create table scripts, there is no collation defined in the scripts. If no collation is defined the default latin1_swedish_ci is used. Which looks correct.
>>> Even when I manually change table collation, when I update, the collation reverts.
That’s strange! An update modifies the table content, not the definition.
Does utf8mb4_unicode_520_ci exist on your server? Did the alter table statement succeed? Please check in the Query Builder:
show character set
Shouldn’t utf8mb4_unicode_520_ci be utf8mb3_general_ci?
Please let us know if this help,
Peter
Greetings,
Thank you for you prompt reply.
You state that latin1_swedish_ci is the collation that the plugin should be installed.
However WordPress specifications state that creating tables from plugin must inherit wordpress collation.
https://codex.ww.wp.xz.cn/Creating_Tables_with_Plugins
Regarding the issue of update, I should clarify I was talking about plugin update. The plugin update reverted the collation.
-
This reply was modified 3 years, 6 months ago by
kabbill21.
>>> Regarding the issue of update, I should clarify I was talking about plugin update.
>>> The plugin update reverted the collation.
Okay, that info helps! 👍 We’ll look into this and let you know.
Thanks,
Peter
Thank you,
Bear in mind that especially table wp_wpda_publisher holds the column aliases for tables. Therefore, if this table has different collation than WordPress, or even custom user tables created with WP Access, column headers are shown as question marks…
Thank you in advance for your help,
Vasilis
Thanks for the additional info Vasilis! I never thought of that… 🙈
Thanks,
Peter
Hi Vasiles,
Tomorrow we’ll release an update. The update contains a fix for the collation issue. I’ll mark this thread as resolved. Feel free to create a new thread if you have other questions.
Thank you for reporting this issue,
Peter