|
Hello WPML Support Team,
I’m facing a critical issue when activating WPML String Translation on a WordPress site.
Environment details:
WordPress: latest version
PHP: 8.2
MySQL: Hostinger (MariaDB)
Database character set: utf8mb4
Database collation: utf8mb4_unicode_ci
Problem:
WPML core installs and activates correctly.
However, when I activate WPML String Translation, the site crashes with a fatal error related to database collation.
Exact error message:
WordPress database error:
COLLATION 'utf8mb3_uca1400_ai_ci' is not valid for CHARACTER SET 'utf8mb4'
CREATE TABLE IF NOT EXISTS wp_icl_string_packages (...)
DEFAULT CHARACTER SET utf8mb4
COLLATE utf8mb3_uca1400_ai_ci;
This causes a fatal exception:
Uncaught Exception:
COLLATION 'utf8mb3_uca1400_ai_ci' is not valid for CHARACTER SET 'utf8mb4'
What I have already tried:
Verified database charset and collation (utf8mb4 / utf8mb4_unicode_ci)
Reinstalled WPML and String Translation from scratch
Removed all existing wp_icl_* tables
Disabled all other plugins
Tested on a fresh WordPress installation
Confirmed the issue occurs only when activating String Translation
It appears WPML String Translation is attempting to create tables using:
CHARACTER SET utf8mb4
COLLATE utf8mb3_uca1400_ai_ci
which is invalid on MySQL/MariaDB.
Request:
Could you please advise:
Why WPML String Translation is using utf8mb3_uca1400_ai_ci?
Is there a recommended fix or patch?
Is this a known compatibility issue with newer MySQL/MariaDB versions?
I’m happy to provide logs, database access, or run any debug steps you recommend.
Thank you for your support.
|
