Problem: The client is trying to translate a page from French to English using both automatic translation and human reviewing, but the English page is not visible after translation. Instead, the page remains in French. Additionally, the 'automatic translation' button on individual segments is not functioning. Solution: Ensure you have selected the 'Translate What You Choose' option in WPML>>Settings>>Translation Mode. Follow these steps: 1) Open the Page for editing in the default language. 2) Make a minor change and update it. 3) Go to WPML>>Translation Management Dashboard. 4) Choose the Page you want to translate or update the existing translations. 5) Send it to the Translation Basket. 6) Go to WPML>>Translation Management>>Translation Basket. 7) Send it for translation, selecting yourself as the translator. 8) Go to WPML>>Translations queue and click the 'Translate' button. For more detailed instructions, refer to this documentation. If the issue persists, please provide screenshots for a better understanding, especially regarding why the 'automatic translation' button is not working on individual segments.
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 needed, please open a new support ticket for further assistance.
Problème: Les traductions de nouveaux produits ne fonctionnent plus sur le site, bloquant ainsi les produits dans une seule langue. Solution: Si vous rencontrez ce problème, nous vous recommandons de suivre ces étapes pour réinitialiser les traductions : 1. Allez dans WPML > Support > Troubleshooting. 2. Cliquez sur tous les boutons disponibles pour le dépannage. 3. Ensuite, naviguez vers WPML > Paramètres > Mode de traduction. 4. Changez le mode à 'Traduire ce que vous choisissez', puis revenez à 'Traduire tout automatiquement'. Cela devrait réinitialiser le processus de traduction et permettre l'envoi des produits à la traduction automatique.
Si cette solution ne résout pas votre problème ou semble obsolète, nous vous recommandons vivement de vérifier les problèmes connus, 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.
Problem: The client is unable to translate links within ACF repeater fields in the Advanced Translation Editor (ATE) on their custom-themed website. The links do not appear for translation in the ATE, although other elements like URLs and text links are visible and translatable. Solution: First, ensure that the button link URL is searchable in the Translation Editor screen. For more details on how to translate URLs, shortcodes, and HTML attributes using the ATE, visit https://wpml.org/faq/how-to-translate-urls-shortcodes-and-html-attributes-using-the-advanced-translation-editor/. If the issue persists, it might be related to a known issue with translating links in ACF repeater fields. We recommend trying the workaround suggested in the following forum post after a full site backup: https://wpml.org/forums/topic/cannot-add-translation-to-acf-button-field-label/#post-15403863. Additionally, check the translation settings for ACF Block Field Groups created using JSON files, as these might not be set correctly.
If these steps do not resolve the issue, or if the solution becomes 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 for further assistance.
Problem: After translating a new page, the client noticed layout changes such as different padding on the top and navigation menu color changes. Solution: We recommended the following steps to address the layout issues after translation: 1. Increase the WP Memory Limit to at least 128MB, as per WPML's minimum requirements. This can be done by adding the following lines to the wp-config.php file:
2. Make a minor edit to the default language page and update it twice, first with the change and then reverting it. 3. Ensure the translation is 100% complete in the WPML Translation Editor. 4.Please make sure the correct template is selected. 5. Clear all types of caches including site/server, plugin, CDN, and browser caches.
If these steps do not resolve the issue or if the solution becomes 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: You are trying to get the Divi Pixel Popup Maker to work on translated pages. While it works on the English version, the popups do not appear on the Spanish version; instead, the page just refreshes when buttons are clicked. Solution: We noticed that the popup was triggering based on the popup CSS ID selector, and the translated popup has a unique ID which needs to be updated on the translated page. Also, the secondary language popup status was inactive. Here are the steps we recommend: 1. Go to the Popup Maker page, hover over the popup, and press the Quick Edit button. 2. Choose the Activate checkbox and press the Update button. 3. Add the following XML in WPML >> Settings > Custom XML Configuration section:
4. Make a small change in the default language page and edit the translated page in WPML Translation Editor. 5. Search for the default language popup ID "dipi_popup_id_22988219" and add the translated popup ID "dipi_popup_id_22988723" as translation. Please try these steps on your live site and see if this resolves the issue.
If this solution does not apply because it might be 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. If the issue persists, please open a new support ticket.
