Problem: The client reported a critical error on the Swedish translation of their website, preventing it from displaying correctly in the frontend. Solution: We identified that the issue was due to incorrect translation of placeholders in strings. Here are the steps we recommended and implemented to resolve the issue: 1. Navigate to WPML >> String Translation. 2. Search for strings containing the placeholder %s. 3. Correct the translation in the Swedish language. For example, we changed the string:
Använd %1$anpassad CSS%3$ för att styla ditt innehåll eller lägg till %2$prefixet "selector"%3$ för att rikta in dig på specifika element.
To:
Använd %1$s anpassad CSS%3$ för att styla ditt innehåll eller lägg till %2$s prefixet "selector"%3$ för att rikta in dig på specifika element.
After making these corrections, the Swedish pages loaded correctly.
If this solution does not resolve your issue or seems irrelevant due to being 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 problem persists, please open a new support ticket.
Problema: Estás intentando traducir un texto en tu sitio web y no encuentras el texto que quieres traducir. El sitio está disponible en inglés y español, pero los idiomas adicionales (alemán, francés e italiano) aparecen en español. Solución: Si estás experimentando este problema, podría deberse al uso de bloques. Te recomendamos seguir los pasos indicados en el siguiente enlace: https://wpml.org/errata/woocommerce-multilingual-cart-page-strings-not-translated-when-using-blocks/. Es necesario reemplazar los bloques por el shortcode estándar de WooCommerce.
Si esta solución no resuelve tu problema o parece no ser relevante debido a que está desactualizada o no se ajusta a tu caso, te sugerimos abrir un nuevo ticket de soporte. Te recomendamos encarecidamente revisar los problemas conocidos en https://wpml.org/known-issues/, verificar la versión de la solución permanente y confirmar que tienes instaladas las últimas versiones de los temas y plugins. Para más asistencia, visita nuestro foro de soporte en https://wpml.org/es/forums/forum/ayuda-en-espanol/.
Problem:
The client was experiencing following critical error when loading blog posts using WPML 4.7.4, and after rolling back to a previous version, some translators were unable to access translation jobs.
Uncaught TypeError: WPML\PB\Elementor\DataConvert::serialize(): Argument #1 ($data) must be of type array, null given
Solution: We identified that the issue with the critical error was related to a known problem documented in our errata. We recommended applying the workaround mentioned in the errata, which can be found here: https://wpml.org/errata/elementor-critical-error-on-woocommerce-product-pages/. We advised the client to apply this solution on their live site after taking a backup. Additionally, we suggested subscribing to the comments of the errata to stay updated on any developments.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: After performing MEDIA TRANSLATION in WPML, the header image on all Spanish language posts and pages appears broken. Solution: We recommend checking the issue related to SVG support when activating WPML Media, which might be stripping parts of the image URL. You can find detailed information and a potential fix here: SVG Support - Activating WPML Media strips uploads folders from SVG image URL. If the header image remains broken after applying the suggested fix, please try re-uploading the image. If these steps do not resolve the issue, it might be due to a different cause or the solution might be 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 the problem persists, please do not hesitate to open a new support ticket for further assistance. You can do so here: WPML Support Forum.
Problème : Vous tentez de traduire des projets du français à l'allemand sur votre site WordPress utilisant le thème Divi, et vous observez que sur certains projets, la catégorie traduite en allemand s'affiche deux fois. Solution : 1. Nous avons identifié que ce problème pourrait être lié à un problème connu avec Divi où les catégories des posts créés dans l'éditeur frontal sont dupliquées. Vous pouvez consulter ce problème connu et la solution suggérée ici : https://wpml.org/errata/divi-posts-created-in-front-editor-have-duplicated-categories/ 2. Si cette solution ne résout pas le problème, nous vous recommandons de synchroniser les taxonomies des projets via WPML > Support > Troubleshooting. Cette action a aidé à supprimer les catégories doublées.
Si cette solution ne semble pas pertinente ou est obsolète, ou si le problème persiste, nous vous recommandons vivement de vérifier les problèmes connus sur https://wpml.org/known-issues/, de vérifier la version du correctif permanent et de confirmer que vous avez installé les dernières versions des thèmes et plugins. Si nécessaire, n'hésitez pas à ouvrir un nouveau ticket de support sur le forum de support WPML.
Problème : Si vous rencontrez une erreur critique sur votre site en utilisant WPML et Elementor, où le message d'erreur indique un problème avec la fonction
serialize()
qui attend un tableau mais reçoit une valeur nulle, cela peut être dû à un problème connu. Solution : Nous vous recommandons de consulter le rapport d'erreur connu sur https://wpml.org/errata/elementor-critical-error-on-woocommerce-product-pages/ et d'appliquer la solution proposée. Si cette solution ne résout pas le problème ou si elle semble obsolète, nous vous conseillons de vérifier que vous avez installé les dernières versions de vos thèmes et plugins. Pour plus d'assistance, n'hésitez pas à ouvrir un nouveau ticket de support sur notre forum de support. Nous vous recommandons également de consulter régulièrement la page des problèmes connus : https://wpml.org/known-issues/ pour vérifier si une version permanente de la correction a été publiée.
Problem: If you're experiencing issues where the content of translated posts is overwritten by the default language's content upon publishing, even if the post is published in the original language first, you are not alone. This problem persists even after following the workaround suggested in the WPML errata. Solution: We recommend trying to deactivate the String Translation plugin to see if this resolves the issue. However, we understand that deactivating the String Translation plugin may not be feasible for many sites due to dependency on the plugin. Unfortunately, currently, deactivating WPML String Translation is the only solution we can offer for this specific problem. A WPML Update that solves this issue is planned for Monday the 19th of May 2025.
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.
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.
