Dear Sir,
I have db encoding enabled as per bellow in my config - settings.php file:
* @global string $CONFIG->dbencoding
*/
$CONFIG->dbencoding = 'utf8mb4';
I have two questions:
Q1. Should Tables and Column (Collations) be set to = "utf8mb4_general_ci" or it should be "utf8mb4_unicode_ci"?
Q2. Should I declare chareset in .htaccess as AddCharset UTF-8 .utf8 ?
I would really appreciate a kind answer.
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 - 1 like
- iionly@iionly
iionly - 1 like
- MyHoTFB.COM ®@myHoTFB
MyHoTFB.COM ® - 0 likes
- MyHoTFB.COM ®@myHoTFB
MyHoTFB.COM ® - 0 likes
You must log in to post replies.Very recommend to read https://mathiasbynens.be/notes/mysql-utf8mb4
Of course, don't forget about GGL
Elgg 3 creates the tables of its database with the correct collation on new installs. Also, Elgg deals with migrating the database on its own when upgrading from 2.3 to 3. So, you wouldn't have to do anything. I also don't think you would have to add anything about charset in .htaccess. I think Elgg adds it to the page header on its own.
@iionly, thanks for the feedback. When Elgg 3 stable release is available, I will go for an upgrade, and as suggested by you migration would be automatic.
@rivervanrain,
Thanks for both the links, which answers my Q1. Thank you sir. Thanks for your help. Appreciated.