Has anyone had experience running Elgg2.3.7 with MySQL8?
One of my servers still uses Elgg 2.3.7. But this server's MySQL is version 8. I noticed that Elgg 2.3.7 uses utf8 (utf8mb3). While MySQL 8's default charset is utf8mb4. Is it safe to update Elgg tables from utf8 to utf8mb4? or is there a better/systematic approach to update the DB charset?
Additional Info of the server: CentOS 8, PHP 7.4, Apache 2.4.
Thanks so much in advance!
info@elgg.org
Security issues should be reported to security@elgg.org!
©2014 the Elgg Foundation
Elgg is a registered trademark of Thematic Networks.
Cover image by RaĆ¼l Utrera is used under Creative Commons license.
Icons by Flaticon and FontAwesome.
- Nikolai Shcherbin@rivervanrain
Nikolai Shcherbin - 0 likes
- Jerome Bakker@jeabakker
Jerome Bakker - 0 likes
- http://learn.elgg.org/en/stable/appendix/upgrade-notes/2.x-to-3.0.html#schema-changes
- http://learn.elgg.org/en/stable/appendix/upgrade-notes/2.x-to-3.0.html#new-mysql-schema-features-are-not-applied
- seri_ng@seri_ng
seri_ng - 0 likes
- seri_ng@seri_ng
seri_ng - 1 like
You must log in to post replies.You can read our discussion about this
Update to Elgg 3.3 ;)
A few changes were made to the MySQL schema
@Nikolai, thanks for the discussion link.
@Jerome, "Update to Elgg 3.3 ;)" will definitely solve this problem :) I have 2 servers running Elgg 3.3.15 and there are no charset issues. However, I still have three servers running Elgg 2.3.x which are planned to upgrade to Elgg 3.3.x. Thanks for the links to the upgrade notes.
Cheers!
Just wanted to share with Elgg community if someone wanted to get utf8mb4 working on Elgg 2.3.x. It is impossible to achieve this unless you modify core code (engine/classes/Elgg/Database.php) which is not recommended by the Core developer team. So, the only alternative is to upgrade to Elgg 3.x as Jerome suggested above.