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.
Problem: The client reported an issue where the visual translator was not displaying correctly in Firefox for certain products on their WooCommerce site, despite working in other browsers like Edge and Chrome. Solution: We attempted to replicate the issue by following the same steps the client provided but were unable to see the problem. This suggests that the issue might be specific to the version of Firefox being used. If you're experiencing this, we recommend trying the following steps: 1. Ensure your browser is up to date. 2. Clear your browser cache and cookies. 3. Try accessing the visual translator in a different browser to confirm if the issue persists.
If these steps do not resolve the issue, it might be outdated or specific 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 continues, please open a new support ticket.
If this solution does not resolve your issue or 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 the problem persists, please open a new support ticket at WPML support forum.
Problem: The client has installed the WPML plugin and followed steps to reduce the size of the icl_translate_job and other WPML tables by removing suggested job IDs and optimizing the tables. Despite these efforts, the table remains over 200MB, causing issues with database copying.
Solution: We reviewed the situation and found that a table size of 200MB for a site with 26 languages and extensive content is reasonable.
Upon further investigation, we used a sample query to analyze the contents of the translation_id and confirmed that the large size is justified due to the substantial content stored, with no duplicate elements found.
If this solution does not apply or is outdated, or if the problem persists, we 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 needed, please open a new support ticket at WPML support forum.
Problem: The client is experiencing an issue where the Tutor LMS email template, translated into Estonian and Russian, is only sending messages in English. Solution: We recommend checking the specific errata page for this issue on the WPML website. Please visit this page for more information.
If this solution does not resolve your issue or 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 contact us directly at the WPML support forum.
Problem: The client needs the same category slug for certain product categories across original and translated languages. However, WPML defaults to the original slug and adds a suffix with the short language code for the translation. Attempts to manually set the same slug are not saved, and WPML may revert the slug or add a '-2' suffix. Solution: We recommend using the 'Quick Edit' option to manually set the same slug for categories in different languages. Here are the steps to follow: 1. Navigate to Products >> Categories list page. 2. Use the admin language switcher to select the secondary language. 3. Click the 'Quick Edit' link on the category you wish to update. 4. Change the slug and press the 'Update category' button. For more details on this issue, you can check the errata page here: https://wpml.org/errata/translated-term-slug-identical-to-the-original-term-slug/
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.
