WPML does not support new WordPress locale pt_PT_ao90

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

Sun	Mon	Tue	Wed	Thu	Fri	Sat
-	9:00 – 14:00	9:00 – 14:00	9:00 – 14:00	9:00 – 14:00	9:00 – 14:00	-
-	19:00 – 22:00	19:00 – 22:00	19:00 – 22:00	19:00 – 22:00	19:00 – 22:00	-

Supporter timezone: Europe/Paris (GMT+02:00)

This topic contains 15 replies, has 3 voices.

Last updated by omerA-2 5 years, 3 months ago.

Assisted by: Yvette.

Author	Posts
August 28, 2019 at 12:56 am #4470209
omerA-2	Hi, I have also been experiencing this (or similar) issue: PHP Fatal error: Uncaught RuntimeException: Language of wp-content/themes/_tk/languages/fr_FR.UTF-8.mo cannot be recognized in /var/www/wp-content/plugins/wpml-string-translation/classes/translations-file-scan/translations-file/wpml-st-translations-file-locale.php:54 It seems it can't determine the language of this file perhaps because of the .UTF-8 encoding appended. In some cases this just logs an error, in some cases the page has a fatal error before the footer completes, and recently it causes my wp-cli command to fail before completing. It appears this is because the php function pathinfo() will return anything in the filename after the first '.' which is 'UTF-8.mo' in this case, so it doesn't match the case statement for 'mo' and falls through to the default and throws an error.

Author

Posts

August 28, 2019 at 12:56 am #4470209

omerA-2

Hi,

I have also been experiencing this (or similar) issue:

PHP Fatal error:  Uncaught RuntimeException: Language of wp-content/themes/_tk/languages/fr_FR.UTF-8.mo cannot be recognized in /var/www/wp-content/plugins/wpml-string-translation/classes/translations-file-scan/translations-file/wpml-st-translations-file-locale.php:54

It seems it can't determine the language of this file perhaps because of the .UTF-8 encoding appended. In some cases this just logs an error, in some cases the page has a fatal error before the footer completes, and recently it causes my wp-cli command to fail before completing.

It appears this is because the php function pathinfo() will return anything in the filename after the first '.' which is 'UTF-8.mo' in this case, so it doesn't match the case statement for 'mo' and falls through to the default and throws an error.