Problem: If you're experiencing issues with line breaks not being translated when using WPML to apply translations to content, this might be due to a known issue with WPML's handling of newlines.
If this solution does not apply to your case, or if it seems outdated, we highly recommend opening a new support ticket. Additionally, 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. For further assistance, you can also visit our support forum at https://wpml.org/forums/forum/english-support/.
Problema: Stai utilizzando Avada Theme e hai creato un Off Canvas. C'è un text box che non viene tradotto, nonostante sembri essere stato tradotto sia dall'editor di WordPress sia dall'editor di WPML. Il testo in alto dovrebbe essere 'Loka', ma appare 'Close' come in inglese. Soluzione: Il problema che stai riscontrando potrebbe essere legato a un problema noto con Avada Theme. Ti consigliamo di provare il workaround disponibile a questo link: https://wpml.org/errata/avada-new-off-canvas-elements-not-appearing-as-translated-in-the-front-end/.
Se la soluzione proposta non risolve il problema o se sembra non essere più rilevante, ti invitiamo a verificare la versione della correzione permanente e a confermare che hai installato le ultime versioni dei temi e dei plugin. Inoltre, ti consigliamo di consultare la pagina dei problemi noti (https://wpml.org/known-issues/) per ulteriori informazioni. Se il problema persiste, ti invitiamo a aprire un nuovo ticket di supporto.
Problem: You are trying to translate Elementor templates using WPML, but automatic translations are stuck, and errors appear. Instead of pencils, gear icons are displayed in the translation interface, and templates remain untranslated even after completing the automatic translation. Solution: The issue might be due to a cache feature introduced by Elementor that conflicts with WPML. We have documented this problem and provided a workaround: Elementor translated pages show stale content after being updated To resolve this, follow these steps: - Navigate to
Elementor > Settings > Performance
page. - Disable the Elementor cache.
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 open a new support ticket at WPML support forum.
Problem: You are using the Salient Nectar Slider on your site and facing issues where the slider images are only displaying in the core language and not in other languages. Additionally, you are inquiring if it's possible to automatically translate URLs to include the correct language code, such as /en. Solution: If you're experiencing this issue, it seems to be a known problem with the Salient Nectar Slider. We recommend checking out the workaround provided in the WPML errata page. Please ensure to backup your database before making any changes. You can find the workaround here: https://wpml.org/errata/salient-theme-nectar-slider-internal-url-is-not-adjusted-automatically/
If this solution does not apply to your case, or if it seems outdated, we highly recommend opening a new support ticket. Also, 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.
Problem: You are experiencing an issue with WPML's Advanced Translation Editor where the progress bar shows that some segments are not translated or validated, even though all segments have been translated. Additionally, you are unable to click the 'Complete Translation' button, and the translations are not displaying on your site. Solution: We recommend trying the previous version of the Advanced Translation Editor (ATE) as there are known issues with the current version that might be causing these problems. For more details on the specific issue related to line breaks being ignored, please visit https://wpml.org/errata/line-breaks-are-ignored-when-using-the-advanced-translation-edior/.
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. Should you need further assistance, please open a new support ticket at WPML support forum.
Problem: The client is trying to translate a page on their website but is encountering issues with incorrect spacing in the translation. The expected URL for the translated page does not display the content with the correct spacing. Solution: 1. We recommended checking the errata related to line breaks being ignored in the Advanced Translation Editor (ATE). For more details, visit https://wpml.org/errata/line-breaks-are-ignored-when-using-the-advanced-translation-edior/. 2. If using the ATE, ensure to open the translation and look for the gear icon in the top right corner of the editor to access additional settings. 3. If using the Classic Translation Editor, check the HTML tab for any missing
<br>
tags that might be causing spacing issues. 4. If the issue persists, we may need temporary access to the site to further diagnose the problem. Before providing access, ensure a full backup of the site and database is taken, using tools like the Duplicator plugin: http://wordpress.org/plugins/duplicator/.
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 for further assistance at WPML support forum.
Problema: Nel tuo sito sviluppato con il tema Avada, una stringa nel footer che contiene delle parole separate da 6 spazi si traduce in modo errato con WPML, trasformando gli spazi in 'a_capo'. Soluzione: Il problema che stai riscontrando è già noto e discusso in dettaglio qui. La soluzione consiste nel disabilitare l'opzione che causa questo comportamento nel traduttore avanzato di WPML. Se dopo questa modifica incontri ancora problemi, ti consigliamo di verificare che tu abbia installato le versioni più recenti dei temi e dei plugin. Inoltre, ti invitiamo a consultare la pagina dei problemi noti per verificare se esiste una soluzione permanente specifica per la tua versione di WPML.
Se il problema persiste o le informazioni fornite risultano non pertinenti o obsolete, ti invitiamo a aprire un nuovo ticket di supporto.
Problem: You are using Bricks builder 1.10.3 and WPML, and you encounter an issue where the Dutch translation of a page appears empty even though it has been translated. Solution: We recommend checking the workaround on this page. First, disable the "I prefer bigger segments" option. Then, update the page in the default language and subsequently update its translation.
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. Should you need further assistance, please open a new support ticket at WPML support forum.
Problem: The client is experiencing an issue where the WPML MySQL database is too large. Solution: We recommend following the steps outlined on the WPML documentation page to reduce the size of the WPML MySQL database.
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.
Problème : Vous tentez de supprimer toutes les données des langues arabe, russe, espagnol, anglais après les avoir désactivées, mais la requête SQL
SELECT * FROM wp_posts WHERE ID IN ( SELECT element_id FROM wp_icl_translations WHERE language_code = 'en' );
retourne 245 résultats au lieu de 0, et des résultats en français. De plus, le tableau des données de langues à supprimer dans la page LANGUES de WPML n'est pas vide comme attendu. Solution : Il est nécessaire de supprimer manuellement les taxonomies. Nous avons identifié un problème connu où les taxonomies ne sont pas supprimées avec l'option de suppression de contenu de la base de données. Vous pouvez consulter les détails ici : https://wpml.org/errata/taxonomies-are-not-deleted-with-the-delete-content-from-database-option/. Nos développeurs travaillent actuellement sur ce problème.
Si cette solution ne résout pas votre problème ou semble obsolète, nous vous recommandons 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 le problème persiste, n'hésitez pas à ouvrir un nouveau ticket de support sur notre forum de support.
Problème : Les tables WPML yng_icl_translation_status et yng_icl_translate sont devenues très volumineuses, occupant une part significative de la base de données. Malgré l'utilisation du plugin wpml_delete_jobs, la taille des tables n'a pas été réduite efficacement. Solution : Si vous rencontrez ce problème, nous vous recommandons de suivre ces étapes pour optimiser et réduire la taille de vos tables WPML : 1. Exécutez le processus de réduction de la taille des tables WPML en suivant ce guide : https://wpml.org/errata/reducing-size-of-icl_translate_job-icl_translate-and-other-wpml-tables/ 2. Avant de lancer le processus, faites des captures d'écran des tailles des tables de base de données avant et après pour comparer. 3. Vérifiez si le processus se termine avec succès ou si des erreurs apparaissent dans la console du navigateur ou ailleurs dans le backend. 4. Si le problème persiste, essayez les commandes suivantes :
OPTIMIZE TABLE nom_de_votre_table;
Cette commande défragmente la table, récupère l'espace inutilisé et réorganise les données. Pour les tables InnoDB, cela peut prendre plus de temps.
ALTER TABLE nom_de_votre_table ENGINE=InnoDB;
Cette commande reconstruit la table et les index, aidant à récupérer l'espace utilisé par les index fragmentés. 5. Ajustez les paramètres InnoDB dans MySQL pour purger plus fréquemment les logs de transactions, en modifiant par exemple la variable
innodb_purge_interval
.
Si ces solutions ne résolvent pas votre problème ou si elles semblent obsolètes ou inapplicables à votre cas, nous vous recommandons vivement de consulter 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.
