Problem: You are experiencing difficulty in finding specific strings in WPML > String Translation due to the abundance of bricks-* or gutenberg-* domains. Solution: Currently, it is not possible to hide bricks-* or gutenberg-* domains directly in WPML > String Translation. To address this issue, you would need to implement custom coding. However, this solution falls outside our support scope, and we do not have a ready-made code snippet available.
If this solution does not apply to your situation, or if it seems outdated, we recommend opening a new support ticket. We also advise checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. For further assistance, please visit our support forum.
Problem: The client changed the default locale from 'en_US' to 'en_GB' in WPML, and the translations for 'Gridbuilder ᵂᴾ' are not appearing on the English pages despite being visible in WPML > String Translation. Solution: We recommend regenerating the MO files to ensure WPML pulls the strings from the correct locale. Please navigate to WPML -> Support -> Troubleshooting and click the 'Show custom MO Files Pre-generation' dialog box button. Then, click the blue button to regenerate custom MO files. If this does not resolve the issue, it may be necessary to manually create and rename copies of the MO files to match the new language locale. For detailed steps, please visit https://wpml.org/errata/string-translations-are-not-displayed-when-a-language-locale-is-changed/.
If the solution provided does not apply or is outdated, or if you encounter further issues, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. Should you need additional assistance, please do not hesitate to open a new support ticket.
Problem: The client was unable to add Dutch (Belgium) with the locale code 'nl_BE' to their WPML languages, receiving an error that the default locale already exists, despite it not being visible in the WPML > Languages > Add / Remove languages section. Solution: We recommended the client to check their database table
_icl_languages
for any entries with a default locale set to 'nl_BE'. Upon inspection, it was found that the locale should have been 'nl_NL'. The client corrected these values in their database, which resolved the issue and allowed them to add Dutch (Belgium) as a custom language.
If this solution does not apply to your case, or if it seems outdated, we highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If issues persist, please open a new support ticket.
