Problem: El cliente tiene dificultades para traducir el contenido de Slider Revolution en varias páginas usando créditos de traducción, a pesar de seguir los procesos de WPML. Solution: 1. Asegúrate de que los ajustes de WPML estén activados en tu Slider Revolution: - Ve a Slider Revolution en tu escritorio de WordPress. - Selecciona el slider que deseas traducir y haz clic en el icono de configuración para acceder a las Opciones generales del módulo. - En la pestaña General, desplázate hasta la parte inferior y activa la opción Usar ajustes de WPML. - Haz clic en Guardar. 2. Si el icono de configuración no es visible, puede aparecer como un engranaje o una rueda dentada al pasar el ratón por encima del nombre del slider. 3. Para traducir el contenido de Slider Revolution correctamente, sigue estos pasos adicionales: - Mueve el texto de Global Slides a una capa común y duplica la capa para traducir el texto y asignarle el idioma deseado. - En otras URLs, registra el elemento, traduce las categorías de las entradas y las entradas asociadas, y cambia el ID de la categoría en el editor de traducción por el ID en el idioma deseado.
Si esta solución no resuelve tu problema o si la información proporcionada se ha vuelto obsoleta, te recomendamos abrir un nuevo ticket de soporte. También es aconsejable revisar los problemas conocidos y confirmar que tienes instaladas las últimas versiones de los temas y plugins. Para más asistencia, visita nuestro foro de soporte.
Problem: If you're experiencing an issue where your Translation Dashboard is empty, it might be due to a critical error on the page. Solution: We recommend enabling WordPress debugging to identify the specific error. Here are the steps you should follow: 1. Edit your wp-config.php file to enable debugging. Insert these lines before the comment /* That's all, stop editing! Happy publishing. */:
2. Replicate the error by accessing the Translation Dashboard again. 3. Check the debug.log file located in your /wp-content directory for any WPML-related errors. 4. Share the full error message with us for further assistance.
Please note that this solution might be outdated or not applicable 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 issue persists, please open a new support ticket.
Проблема: Клиент столкнулся с проблемой, что при использовании функции "Copy from original language if translation language uses encoded URLs" и переводе через редактор ATE, ссылка на странице перевода формируется по переведенному названию, а не копируется оригинальный слаг. Клиенту приходится вручную корректировать слаг в редакторе WP-Gutenberg и очищать кеш. Решение: Мы рекомендуем убедиться, что для нужных языков установлен параметр Encode URLs = Yes. Это можно сделать в WPML → Languages → Edit Languages. Также, если клиент хочет начать перевод с абсолютного нуля, мы можем очистить память переводов (ATE), что позволит удалить все сохранённые переводы памяти для сайта, не затрагивая завершенные переводы. Подробнее о памяти переводов можно узнать здесь: https://wpml.org/documentation/translating-your-contents/how-wpml-keeps-track-of-your-translations/
Если данное решение окажется неактуальным или не поможет в вашем случае, мы настоятельно рекомендуем проверить известные проблемы, убедиться в актуальности версии исправления и подтвердить, что у вас установлены последние версии тем и плагинов. Если проблема сохранится, пожалуйста, откройте новый тикет поддержки.
Problem: You are trying to automatically translate image captions and titles using custom ACF blocks with gallery fields, but they are not being recognized by the advanced translation editor. This issue does not occur with ACF fields used directly as a page field. Solution: First, ensure that your image (gallery) field has the correct translation settings. You can check the official guide here: Translating ACF Blocks. Next, in WPML: - Go to WPML → Settings - Locate the option to include media texts (captions, titles, alt text) in the Advanced Translation Editor and ensure it is enabled. After updating these settings: - Update the original page - Re-send it for translation - Complete the translation again If the image captions and titles still do not appear in the translation editor, it might be due to a caching issue or a need for further configuration adjustments. In such cases, disabling Object Cache, running a local ACF sync, and making a minor change to the page before re-sending for translation can help.
If these steps do not resolve the issue, or if the solution becomes outdated, we 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 problem persists, please open a new support ticket.
Problem: You need to configure WPML to prevent a specific message from appearing. Solution: First, check if the issue is related to the REST API on your site. Ensure that the REST API is enabled. For more details, visit https://wpml.org/documentation/support/rest-api-dependencies/. If the message still appears, please upload a screenshot of the error/message and provide the debug information from your site. You can find instructions on how to retrieve and share this information here: http://wpml.org/faq/provide-debug-information-faster-support/.
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 you still need assistance, please open a new support ticket at WPML support forum.
Problem: The client reported an issue with the NV400 product tag not syncing from Bulgarian (BG) to Dutch (HR) and other languages. Additionally, there were concerns about 808 untranslated product labels and tags appearing untranslated across different languages.
Solution: 1. Ensure that all product tags are properly translated into each language. Tags that are not translated will not appear in the product's language version. 2. For the specific NV400 tag, check and translate the tag directly in the WPML interface. Here is the link to manage the translation: Translate NV400 Tag 3. If issues persist, consider creating a staging site to test the product in a minimal environment, disabling other plugins, and using the parent theme to isolate the issue. 4. For general untranslated tags, ensure they are assigned to products in the default language before duplicating or translating.
Please note that this solution might be outdated or not applicable to your specific case. If the problem persists, 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 needed, do not hesitate to open a new support ticket for further assistance at WPML Support Forum.
Problema: El cliente enfrenta problemas con la visualización de traducciones en su sitio web usando WordPress, WooCommerce, y el Divi Theme Builder. Los campos personalizados creados con PODS no se muestran correctamente en el front-end en inglés y español, y en algunos casos, aparecen etiquetas HTML literales. Solución: 1. Cambiar el método de traducción de los campos PODS a traducción manual, siguiendo las instrucciones en https://wpml.org/es/plugin/pods-custom-content-types-and-fields/ y https://wpml.org/documentation/translating-your-contents/using-different-translation-editors-for-different-pages/. 2. Si se utiliza Divi 4, aplicar una personalización en el código para evitar el problema con los campos de PODS. Abrir el archivo
alrededor de la línea 1741 y comentar el bloque de código indicado. 3. Considerar actualizar a Divi 5, ya que el equipo de compatibilidad se centrará en esta versión. 4. Si el problema persiste, contactar con el soporte de Divi para una revisión adicional.
Si esta solución no resuelve tu problema o parece desactualizada, te recomendamos abrir un nuevo ticket de soporte en nuestro foro. También es aconsejable revisar los problemas conocidos en https://wpml.org/known-issues/, verificar la versión de la solución permanente y confirmar que tienes instaladas las últimas versiones de los temas y plugins.
Problem: The client is experiencing issues with WPML on their website where new elements added in the original language do not appear in the translation editor for other languages. Even after translating them, the translated page does not update and remains based on an older layout snapshot. Additionally, some templates and pages do not synchronize across all languages. Solution: We recommend ensuring that you are using the latest versions of WPML and related add-ons. To test synchronization, follow these steps: 1. Make a small change in the default language template, such as adding or modifying a text element. 2. Save the template. 3. Open the translation in the Advanced Translation Editor and complete/save it again. If new elements still do not appear or the translation does not update, temporarily disable any caching or optimization plugins, as these can sometimes cause issues.
If the problem persists, we suggest visiting our known issues page to check for any related known issues, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If these steps do not resolve the issue, please open a new support ticket.
Problem: If you're trying to create a translation by duplicating a page in WPML and it works for all languages except Danish, resulting in a 404 error, even after re-saving permalinks and updating plugins. Solution: 1. Navigate to Settings → Permalinks in your WordPress dashboard. 2. Without making any changes to the settings, simply click the Save Changes button. This action might help refresh the URL rewrite rules across your site, especially after updates or content changes. If this does not resolve the issue, it could be due to a slug conflict with another plugin using the same slug for different content in Danish. In such cases, changing the slug to a unique one should resolve the problem.
Please note that this solution might be outdated or not applicable 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.
