Problème : Vous souhaitez renouveler votre abonnement pour un site spécifique. Solution : Nous vous recommandons de configurer votre renouvellement via votre profil sur wpml.org/account. Si vous désirez conserver toutes les fonctionnalités de WPML tout en limitant votre licence à un seul site, optez pour la licence Multilingual CMS. Vous pouvez trouver plus de détails sur cette licence ici : https://wpml.org/purchase.
Si cette solution ne correspond pas à votre cas ou semble obsolète, nous vous conseillons de vérifier les problèmes connus sur https://wpml.org/known-issues, de vérifier la version de la correction permanente et de vous assurer que vous avez installé les dernières versions des thèmes et plugins. Si le problème persiste, n'hésitez pas à ouvrir un nouveau ticket de support sur notre forum de support.
Problem: The client is using Livecanvas to build sites and has auto-translated all pages. However, editing each language separately in the Livecanvas editor after using the WordPress editor breaks the layout, with some HTML attributes missing. Solution: We recommend not mixing translation methods for the same page or product. If you initially translate a page using the Advanced Translation Editor (ATE) and later switch to the WordPress editor for the same page, the two editors will not synchronize, potentially leading to loss or overwriting of previous translations. To maintain consistency and avoid layout issues, stick to one editor per page or product throughout the translation process.
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. If problems persist, we highly recommend opening a new support ticket at WPML support forum for further assistance.
Problem: If you're trying to update the language to Cyrillic and encounter display issues like 'БългарÑкÐ', this might be due to a database character encoding issue. Solution: We recommend going to WPML → Languages → Site Languages → Edit Languages to modify the display name of each language. Ensure your database tables and columns use a UTF-8 compatible collation, preferably 'utf8mb4_unicode_520_ci'. For more details, visit WPML Minimum Requirements. If you're unsure about making these adjustments, please contact your hosting provider to update the database collation safely.
Please note that this solution might be outdated or not applicable to your specific case. We highly recommend checking related known issues at WPML 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: The Elementor footer is visible only in the main language (Estonian), but not in Finnish and Russian. Solution: If you're experiencing this issue, we recommend following these steps: 1. Visit the Elementor documentation on compatibility with WPML: https://wpml.org/documentation/plugins-compatibility/elementor/ 2. Ensure that the footer template is translated: - Navigate to Elementor → Templates (Theme Builder / My Templates). - Locate the Footer used in Estonian. - Use WPML’s translation controls (plus icon / Translation Dashboard) to create translations for Finnish and Russian for that footer template. - Open each translated footer and confirm it is Published.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: Wenn Sie eine Seite in deutscher Sprache erstellen und dann den Advanced Translation Editor öffnen, um die englische Übersetzung zu erstellen, wird die Übersetzung nicht automatisch durch DeepL erstellt, obwohl Sie dies erwarten. Lösung: Die automatische Übersetzung im Advanced Translation Editor funktioniert nur, wenn sie in den globalen WPML-Einstellungen aktiviert ist. Wenn die globale automatische Übersetzung deaktiviert ist, kann der Editor keine automatische Übersetzung starten, auch wenn der Haken gesetzt ist. In diesem Fall sollte die Option ausgegraut sein. Unsere Entwickler haben das Problem geprüft und konnten es aktuell nicht reproduzieren. Falls die Option bei Ihnen weiterhin aktiv ist, obwohl die globale automatische Übersetzung deaktiviert ist, empfehlen wir Ihnen, uns kurz Bescheid zu geben.
Diese Lösung könnte irrelevant sein, da sie veraltet sein könnte oder nicht auf Ihren Fall zutrifft. Wir empfehlen Ihnen, ein neues Support-Ticket zu öffnen, wenn dies der Fall ist. Wir empfehlen auch, die bekannten Probleme zu überprüfen, die Version der dauerhaften Lösung zu verifizieren und zu bestätigen, dass Sie die neuesten Versionen von Themes und Plugins installiert haben.
Für weitere Unterstützung empfehlen wir Ihnen, ein Ticket im WPML-Support-Forum zu eröffnen.
Problem: The client is using Elementor Pro and WPML on a Hostinger Cloud Starter plan. They have created two templates per language for their website: Header and Footer. While the header templates are translating correctly and changing with the language, the footer templates, which were functioning correctly, stopped working correctly after adding Arabic translations. Solution: To translate Elementor when using WPML, it is required to install the WPML String Translation plugin. This can be done by navigating to Plugins > Add New and selecting the "Commercial" tab in your WordPress dashboard. For detailed guidance on how to translate content created with Elementor using WPML, please visit the following link:
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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: El cliente está experimentando errores HTTP 404 aleatorios en URLs que sí existen y a veces funcionan nuevamente después de recargar la página. Este problema ocurre en un sitio multilingüe usando WPML, Astra, Elementor y Pro Elements, y se manifiesta en todos los idiomas (español, inglés, francés). Solution: Si estás experimentando este problema, te recomendamos revisar el siguiente artículo que describe síntomas muy similares y proporciona pasos sugeridos para resolverlo: https://wpml.org/faq/why-is-htaccess-getting-overwritten-with-the-language-folder-on-my-wpml-website/ Es posible que este problema esté relacionado con reglas de plugins de terceros que llaman a flush rules demasiado a menudo.
Si la solución sugerida no resuelve tu problema o si crees que la información puede estar desactualizada o no aplicarse a tu caso, te recomendamos abrir un nuevo ticket de soporte. También te sugerimos verificar los problemas conocidos en https://wpml.org/known-issues/, confirmar que tienes instaladas las últimas versiones de los temas y plugins, y verificar la versión de la solución permanente. Para más asistencia, visita nuestro foro de soporte en https://wpml.org/es/forums/forum/ayuda-en-espanol/.
Problem: The client is experiencing issues with setting the language slug for Britain to /uk instead of en-GB. Solution: We recommend activating Ukrainian in WPML → Languages. Then, edit the Ukrainian language, changing the language name, locale, and other settings to English. If a warning appears about the English locale being in use, edit the English language to change its default locale to free up the English locale. This allows you to assign it to another language. Since the language code 'uk' is pre-configured for Ukrainian and cannot be changed, this method is necessary. For detailed steps, please visit Editing WPML's Languages Table.
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.
Problem: On your website using WordPress, WooCommerce, and WPML, you are encountering an issue where 6 items in WPML → Translation Dashboard cannot be completed due to an unexpected error. The error messages include 'DownloadError' and 'target should be an object with map method or an array'. Additionally, there is a specific error related to WPML_PB_Handle_Custom_Fields indicating a type issue with the argument. Solution: We recommend following the troubleshooting steps available in WPML > Support > Troubleshooting. These steps have resolved the issue for other clients experiencing similar problems.
If this solution does not resolve your issue or seems irrelevant due to it 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 at WPML support forum for further assistance.
Problem: The client is experiencing issues with content on their multilingual website where certain content reverts to the original English after updates on the German page. Specifically, elements on the page revert to English when they are set as duplicates of the original content. Additionally, there are issues with updating images on another page, which do not reflect changes after publishing. Solution: We recommend ensuring that the pages are set to 'Translate independently' rather than as duplicates of the original content. This setting prevents the content from syncing with the original page and thus reverting to English. To do this: 1. Go to the WPML settings and select the option to 'Translate independently' for the pages in question. 2. Avoid using the duplicate option if you want the content to remain in the translated language without reverting. 3. For further details on how to display untranslated content or set pages to translate independently, please visit https://wpml.org/documentation/translating-your-contents/displaying-untranslated-content-on-pages-in-secondary-languages/.
If these steps do not resolve the issue or if the solution seems outdated or irrelevant to your specific 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 at WPML support forum for further assistance.
Problem: You have changed the slug for your posts page to 'ideas', and your permalink structure is set to /ideas/%postname%/. However, the translated posts still display 'ideas' in the URL instead of the translated version. Solution: We currently do not support translating custom permalink structures directly. As a workaround, you could consider using a Custom Post Type (CPT), as CPT archive slugs can be translated. If switching to a CPT is not feasible, you might: 1. Create a category with the desired slug. 2. Assign this category to all relevant posts. 3. Update your permalink structure to include the category. Since category slugs can be translated, this method allows you to achieve a multilingual URL structure. For more details, please refer to our guides on Translating page slugs and Translating post categories and custom taxonomies.
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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
