Problème : Le client a ajouté un paramètre d'URL pour des tests et, après l'avoir retiré, le panneau d'information de WPML indiquant une nouvelle adresse pour le site est toujours visible. Solution : Si votre site WordPress est configuré pour que deux domaines pointent vers le même site web, WPML peut afficher l'assistant de migration. Pour résoudre ce problème, suivez ces étapes : 1. Accédez à WPML → Support et cliquez sur le lien Dépannage. 2. Sur la page de dépannage, cliquez sur le bouton 'Force-enable WPML's Advanced Translation Editor'. Cela vous permettra d'utiliser l'éditeur de traduction avancé de WPML pour gérer les traductions sur les deux domaines sans voir l'assistant de migration.
Si cette solution ne s'applique pas à votre cas, ou si elle semble obsolète, nous vous recommandons de vérifier les problèmes connus, de vérifier la version de la correction permanente 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.
Problema: El cliente estaba intentando traducir entradas en su sitio usando WPML, pero encontró problemas con el editor de traducción avanzado (ATE) que no conectaba con WPML, y las entradas no se mostraban traducidas en el frontend. Solución: 1. Solicitamos acceso al sitio para revisar el problema más de cerca. 2. Confirmamos que solo había contenido en español y no en Valenciano. 3. Pedimos al cliente que restaurara una copia de seguridad y creara un sitio de pruebas. 4. Realizamos pruebas en el sitio de producción y en una copia local. 5. Escalamos el problema a nuestro segundo nivel de soporte para una revisión más profunda. 6. Identificamos y corregimos un problema en la base de datos relacionado con el código del idioma. 7. Realizamos cambios en una entrada de prueba y confirmamos que la traducción funcionaba correctamente en ambos idiomas.
Si la solución proporcionada no resuelve tu problema o parece no ser relevante debido a que está desactualizada o no se aplica a tu caso, te recomendamos abrir un nuevo ticket de soporte. También te sugerimos revisar los problemas conocidos y confirmar que tienes instaladas las últimas versiones de los temas y plugins. Si necesitas más ayuda, no dudes en contactarnos en el foro de soporte de WPML.
Problem: You are trying to translate content on your site using WPML and encounter an error where translations only save as drafts, and the progress bar indicates unfinished segments. Additionally, after switching back to an older version of the editor to resolve one issue, you face another problem where the option to create a custom URL is not available when enabling 'Translate' in 'Page URL' settings. Solution: If your translations are not saving completely, it might be due to missing HTML formatting markers in the translation. To resolve this, edit the translation that requires the markers and navigate to the specific field in the translation box. You will see the markers available to add. Highlight the content that requires the markers and add them to match the original sentence. Check the results after making these adjustments. For further guidance on using HTML markers in translations, refer to our documentation on Advanced Translation Editor - Safe HTML Editing.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also highly suggest 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. For further assistance, please visit our support forum at WPML Support Forum.
Problem: If you're experiencing issues with translating Elementor Pro Animated Headline Widgets using WPML, where the rotating animated headline on translated pages displays all words at once instead of separately, follow these steps. Solution: First, try adjusting the settings in our Advanced Translation Editor (ATE). Here’s how: 1. Edit the translation in our editor. 2. Click on the Settings icon in the top right corner. 3. Deactivate the option 'I prefer big segments' and complete the translation. If the problem persists, make a small edit to the original page in Elementor by adding a space after one of the rotating texts from the animated widget. This will prompt a retranslation of those smaller segments, open the translation and complete it.
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 you still need assistance, please open a new support ticket at WPML support forum.
Problem: The client launched an automatic page transition on their site using WPML and Elementor, but only 2% of the content was translated, and the credits were removed. Solution: If you're experiencing this issue, it's important to ensure that all Elementor widgets used on your page are compatible with WPML. Widgets not supporting translation by default need to be registered for translation. Specifically, any Elementor template used within the page, like Template ID: 9572 in this case, must be translated separately. We recommend following the steps in our guide on translating Elementor templates to resolve this issue.
If this solution does not apply because it might be outdated or not relevant to your specific case, 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 issues persist, we highly recommend opening a new support ticket for personalized assistance at WPML support forum.
Problem: If you're experiencing issues where the call to action button text reverts back to English after saving the page post adding page-level CSS in Spectra Editor, even though it was initially translated correctly. Solution: We recommend following these steps: 1. Open the default language page in Edit mode. 2. Make a small change, such as adding a '+' sign in the page title. 3. Update the page by pressing the “Update” button. 4. Remove the small change made in step 2. 5. Update the page again. 6. Open the translated page in WPML Translation Editor and ensure the translation is 100% complete, then press the complete button. This should maintain the correct translation on the frontend.
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. Additionally, you can open a new support ticket for further assistance at WPML support forum.
Problem: The client is experiencing issues with translating ACF (Advanced Custom Fields) field data into other languages, even though they have installed the "Advanced Custom Fields Multilingual" plugin. Solution: First, ensure that the ACF Multilingual plugin is active on your site. If it's not, you can install and activate it from Plugins > Add New > Commercial tab. Once activated, navigate to ACF > Custom Fields, open the field group, and configure the translation options for the field group according to your needs. For detailed guidance on setting the translation options, visit setting field group translation options. If you choose the "Expert" translation option, remember to set each field you want to translate to "Translate." After configuring the settings, make a minor change to the default page containing the ACF fields and save it. Then, update the translation. This should make the data available for translation in the editor.
If this solution does not resolve your issue or seems outdated, 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 further assistance is needed, please open a new support ticket.
