Home›Support›English Support›[Escalated to 2nd Tier] WPML does not support new WordPress locale pt_PT_ao90
[Escalated to 2nd Tier] 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.
WordPress 6.7 has introduced a new issue that impact translations, please update WooCommerce and WPML to the latest versions before you report issues. More about this here - https://wpml.org/errata/php-error-wp-6-7-notice-function-_load_textdomain_just_in_time-was-called/
Fatal error:
Fatal error: Uncaught RuntimeException: Language of /home/REMOVED/public_html/wp-content/languages/pt_PT_ao90-1bba9045bb07c89671c88a3f328548e8.json cannot be recognized in /home/infusoescomhisto/public_html/wp-content/plugins/wpml-string-translation/classes/translations-file-scan/translations-file/wpml-st-translations-file-locale.php:54
This happens because on wpml-st-translations-file-locale.php line 49 the "#([a-z]+[_A-Z]*)-[-_a-z0-9]+\.json$#i" pattern can't extract "pt_PT_ao90" from the "https://cdn.wpml.org/home/REMOVED/public_html/wp-content/languages/pt_PT_ao90-1bba9045bb07c89671c88a3f328548e8.json" file name.
Here is a brand new post directly in pt_PT_ao90: hidden link
And here is a Woocommerce product translated to pt_PT_ao90: hidden link
I did have to complete the full configuration of Woocommerce and WCML however. Once I did this - I imported sample products and then tried to translate to PT.
does not expect a locale like "xx_xx_xx99", as stated on lines 24 to 29:
* It extracts language code from mo file path, examples
* 'https://cdn.wpml.org/wp-content/languages/admin-pl_PL.mo' => 'pl'
* 'https://cdn.wpml.org/wp-content/plugins/sitepress/sitepress-hr.mo' => 'hr'
* 'https://cdn.wpml.org/wp-content/languages/fr_FR-4gh5e6d3g5s33d6gg51zas2.json' => 'fr_FR'
* 'https://cdn.wpml.org/wp-content/plugins/my-plugin/languages/-my-plugin-fr_FR-my-handler.json' => 'fr_FR'
I'll investigate when this is needed so we can replicate it on the sandbox website, but the information I'm providing on this reply is enough to understand that there is, in fact, a problem.
I don´t doubt at all that there is an issue as you describe.
However, on my end I do need to follow our own protocols so that I can escalate the problem to development. For this, my job is to replicate the issue on a clean sandbox site.
They will then work directly on this site with the recreated issue to investigate the problem and develop a solution.
I wanted to update you on the work regarding this issue. Our 3rd tier support has been able to confirm/replicate the problem and it is now in the hands of our development team for fixing.
