Problem: When saving the original English version of a page, the translated versions (French, Spanish, UK) revert to English. The client follows steps to duplicate the US version of the article and set the duplicated pages to 'Translate Independently'. Solution: Temporarily disable WPML String Translation when creating a new manual translation using the WordPress Editor. This is a known issue detailed here: https://wpml.org/errata/editing-translated-posts-directly-can-result-in-lost-content/.
Note: An update from WPML that addresses this issue is expected soon, though no specific release date is available.
If this solution does not resolve your issue or seems outdated, please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. We highly recommend opening a new support ticket if the problem persists. Visit our support forum here: https://wpml.org/forums/forum/english-support/.
Problem: You are experiencing issues with WPML and ACF repeater fields in a multilingual setup using WordPress Classic Editor. Specifically, when you delete a row or change the order of rows in the default language, the translated versions become misaligned. You are looking for a way to prevent repeater row shifting/desync when editing the default language, maintain translation support only for one subfield while keeping other fields copied or fixed, and avoid full manual reordering and re-entry across all languages. Solution: This issue is related to a known problem currently under investigation by our developers. You can find more details here: https://wpml.org/errata/advanced-custom-fields-multilingual-reordering-repeater-fields-makes-the-translations-unsynchronised/ When using the WordPress Editor to create translations, ensure all ACF Fields are set to "Copy once". This setting ensures that fields are only copied once and then become editable in the translated content. Additionally, set "ACF Field Groups" at WPML > Settings > Post Type Translation to "Not translatable". More details on setting up ACF fields with WPML can be found here: https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/recommended-custom-fields-translation-preferences-for-acf-and-wpml/
If this solution does not apply to your case, or if it seems outdated, 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. If issues persist, please open a new support ticket at our support forum.
Problem: If you're using WPML with WordPress, Elementor, and the Elementor Pro Form widget, and you notice that when translating a form's dropdown field into Italian, the options appear incorrectly as a single string instead of separate lines, resulting in a broken dropdown. Solution: We are aware of this issue and it has been escalated to our developers. A fix is planned for a future release of WPML. You can track updates on this issue by visiting the errata page: Elementor Form Widget Select Field Breaks When Translated with CTE. In the meantime, we recommend using the Advanced Translation Editor (ATE). If you prefer not to use ATE, you can opt for a manual translation approach. For guidance on using different translation editors, please visit: Using Different Translation Editors for Different Pages.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. 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. If the issue persists, please open a new support ticket at WPML support forum.
Problem: You are experiencing a PHP Fatal Error: Uncaught ValueError: Unknown format specifier "t" in wpml-st-translations-file-registration.php on line 100 when using the WPML plugin. Solution: We recommend applying the following workaround to resolve the issue: https://wpml.org/errata/flux-checkout-fatal-error-uncaught-valueerror-unknown-format-specifier-t/ Please ensure to backup your database before making any changes.
If this solution does not apply to your case, or if it seems outdated, 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. If further assistance is needed, please open a new support ticket at WPML support forum.
Problem: O cliente está enfrentando problemas para acessar o Glossário no WPML devido a um erro de conexão com a tradução automática. Solution: Se você está enfrentando esse problema, recomendamos desativar temporariamente o plugin WP External Links. Identificamos que o erro ocorre apenas quando este plugin está ativo. Já estamos em contato com o autor do plugin para uma solução definitiva. Enquanto isso, você pode seguir a solução temporária disponível em https://wpml.org/errata/wp-external-links-plugin-prevents-the-translation-tools-tab-from-loading/.
Se essa solução não for relevante para o seu caso, ou se ela estiver desatualizada, recomendamos abrir um novo ticket de suporte. Também é altamente recomendável verificar problemas conhecidos em https://wpml.org/known-issues/, verificar a versão da correção permanente e confirmar que você instalou as versões mais recentes de temas e plugins. Para mais assistência, visite nosso fórum de suporte em https://wpml.org/forums/forum/portuguese-support/.
Problem: If you're trying to activate the WPML plugin on your WordPress site and encounter a critical error that makes the site inaccessible, this might be due to an issue with string translations. Solution: We recommend following these steps to resolve the issue: 1. Navigate to WPML >> String Translation. 2. Search for the %s string. 3. Correct its translation. After these adjustments, your site should regain accessibility in all configured languages. If the problem persists, it might be related to a known issue with PHP 8, as detailed in our errata: PHP 8 PHP Fatal Error: Uncaught ValueError: Unknown format specifier.
If this solution does not apply because it's outdated or not relevant to your case, 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 further assistance, please open a new support ticket at WPML support forum.
