[Escalated to 2nd Tier] WPML does not support new WordPress locale pt_PT_ao90

Even if we are unable to replicate it on the sandbox website, the problem is in the

PATTERN_SEARCH_LANG_JSON

constant on

wpml-string-translation/classes/translations-file-scan/translations-file/wpml-st-translations-file-locale.php

:

#DOMAIN_PLACEHOLDER([a-z]+[_A-Z]*)-[-_a-z0-9]+\.json$#i

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 know. I'm debugging the issue as we speak so we can replicate it on the sandbox website.

This happens if your wp-admin language is set to PT_pt_a90 or default (and PT_pt_ao90 is the default language).

I've changed the "demo" user language to "default" and you can test it now.

Additional debug:

This happens when:

WPML_ST_Translations_File_Locale->get

(this is the functions that fails when parsing the filename to get the locale)

is called by

WPML_ST_Script_Translations_Hooks->get_file_locale

that is called by

WPML_ST_Script_Translations_Hooks->override_jed_file

that is added to the

load_script_translation_file

filter on

WPML_ST_Script_Translations_Hooks

which is instantiated on

WPML_ST_Script_Translations_Hooks_Factory->get_filtering_hooks

Any news on this?