Problema: Estás intentando traducir algunos productos a otros idiomas en tu sitio web, pero las versiones traducidas muestran un error 404. Esto ocurre con algunos productos, pero no con todos. Solución: 1. Asegúrate de que el slug utilizado para los productos no se haya usado más de una vez en el mismo idioma u otro idioma. WordPress requiere un slug único para cada publicación, página y tipo de publicación. 2. Ve a Configuración > Enlaces permanentes en tu panel de WordPress y guarda la estructura sin hacer cambios. 3. Cambia al idioma secundario usando el selector de idiomas en la parte superior del panel de WordPress. 4. Localiza el producto que muestra el error 404 y ábrelo en el editor de productos. Asegúrate de que el 'Estado' esté configurado como 'Publicado'. 5. Limpia las cachés del sitio y del navegador y verifica nuevamente. 6. Si has eliminado la base de los productos de la URL, reactiva esta opción y guarda nuevamente los enlaces permanentes. 7. Crea una copia de seguridad del sitio completo y actualiza los plugins de WPML en Plugins -> Añadir nuevo -> Pestaña 'Comercial'.
Si la solución proporcionada no resuelve el problema o si el problema persiste, te recomendamos abrir un nuevo ticket de soporte. También te sugerimos revisar los problemas conocidos y verificar que tienes instaladas las últimas versiones de los temas y plugins.
Problem: You are trying to update a page and encountering the error:
WPML didn't manage to translate the page
. Additionally, when translating a product into French by clicking on the plus icon, the translation does not appear on the frontend. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Navigate to WPML-> Translation Management-> Translators tab. 2. Ensure that your account is set as a translator with the correct language pairs. 3. Edit the page in the default language. 4. Add "V2" to the title and update the page. 5. Remove the "V2" and update the page again. 6. Click on the update translation icon and check if the editor opens correctly.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, please open a new support ticket. 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. For further assistance, you can also visit our support forum at WPML Support Forum.
Problem: How to ensure that the translated YITH preset appears on the French version of a page without manually adding the translated shortcode on each French page when using Elementor. Solution: 1) Set the preset to 'Translate Independently' and manually edit the translated filter. For manual translation guidance, see this guide. 2) If using a shortcode in Elementor for the default language, translate the slug within the shortcode. For example, change
[yith_wcan_filters slug="default-preset"]
to
[yith_wcan_filters slug="translated-preset"]
. Register the shortcode for translation by adding XML code in WPML-> Settings-> Custom XML tab. For more details on translating shortcodes, visit this guide. Example XML:
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also 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. For further assistance, please visit our support forum at WPML support forum.
Problem: The client is unable to display translation flags on their website despite deactivating all plugins except WPML and using the standard WordPress theme. The issue persists even after removing all custom CSS. Solution: We discovered that the footer language switcher is actually present but hidden. We recommend checking the settings in the custom CSS section of your theme, which can be accessed here: Theme Custom CSS settings. For the main menu, ensure that the locations are correctly set to display the mega menu where the language switcher should appear.
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.
Problem: If you're experiencing issues with product variants disappearing after updating WooCommerce Multilingual & Multicurrency to version 5.3.9, it might be due to conflicts with other plugins or themes. Solution: We recommend the following steps to troubleshoot and resolve the issue: 1. Ensure that only WooCommerce, WPML, and our addons are enabled when updating to the latest version of WooCommerce Multilingual & Multicurrency. 2. If the issue persists, try enabling all plugins and the child theme again to check if the problem still does not occur. 3. On your live site, delete any minified files created by Assets Cleaner PRO and clear the site's cache before updating. 4. Check for configuration issues under WooCommerce > WooCommerce Multilingual & Multi-Currency > Status. 5. Go to WPML > Settings > Post Type Translation and set "Variations (product_variation)" to "Translatable - only show translated items" and save the settings. 6. In WPML > Settings > Custom Fields Translation, click "Show system fields" and set the field
_crosssell_ids
to "Translate". If these steps do not resolve the issue, the 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.
Problem: El cliente tiene problemas al traducir la sección Blog de su sitio web que utiliza Thrive Architect. Los textos y botones de la plantilla se actualizan en ambos idiomas en lugar de mantenerse específicos para cada idioma. Solution: Primero, asegurarse de que la plantilla esté configurada para traducirse independientemente en WPML. Esto se puede hacer en WPML -> Configuración -> Traducción de tipos de entrada, marcando 'Thrive Template (thrive_template)' como traducible y guardando los cambios. Luego, en WPML -> Administración de traducción, buscar y duplicar la plantilla del Blog llamada 'List Layout With Sidebar'. Finalmente, traducir la plantilla directamente utilizando el enlace proporcionado. Sin embargo, se identificó que Thrive Architect no es compatible con WPML, lo cual puede ser la causa del problema. Se recomienda contactar a los autores de Thrive Architect para obtener un manual específico de traducción si es necesario.
Si esta solución no resuelve el problema o parece desactualizada, recomendamos abrir un nuevo ticket de soporte. También es altamente recomendable revisar los problemas conocidos y verificar que se tiene instalada la última versión de los temas y plugins. Para más asistencia, visite nuestro foro de soporte.
Problem: Вы сталкиваетесь с ошибкой валидации имени пакета при попытке назначить задание, и ресурсы не загружаются по определенным URL. В логах присутствуют ошибки связанные с аутентификацией на сервере ATE. Solution: Если вы столкнулись с подобной проблемой, мы рекомендуем проверить, не блокирует ли ваш сервер запросы к определенным доменам. Вам может потребоваться добавить в белый список следующие домены или обратиться к вашему хостинг-провайдеру для этого:
wpml.org
cdn.wpml.org
api.wpml.org
api.toolset.com
cloudfront.net
После подтверждения, что домены не блокируются, выполните следующие шаги:
Перейдите в Плагины -> Добавить новый -> Реклама на вашем сайте.
Отмените регистрацию WPML, нажав на ссылку отмены регистрации.
Вернитесь в Плагины -> Добавить новый -> Реклама и используйте новый ключ для регистрации.
Если данное решение оказалось неактуальным или не помогло в вашем случае, рекомендуем открыть новый тикет поддержки. Также настоятельно рекомендуем проверить известные проблемы, версию постоянного исправления и убедиться, что у вас установлены последние версии тем и плагинов.
If these steps do not resolve your issue, or if the solution 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.
Problem: The client was unable to change the 'read more' and search placeholder texts in the Dutch language using the Kadence Builder, despite the strings being translated in WPML's String Translation section.
Solution: We discovered that the issue was related to how Kadence Builder's custom fields were registered with WPML. To resolve this, our team created a custom XML configuration to ensure these fields are recognized and translatable by WPML. Here are the steps we followed:
1. We examined the content inside the database of the main query post type to understand how the blocks were structured.
2. We created a custom XML configuration and added it to WPML > Settings > XML config tab. The XML code used was:
3. After saving the XML configuration, we made a small edit and saved the default language edit page, then updated the translated version with the correct placeholder text.
This solution allowed the 'read more' and search placeholder texts to display correctly in both languages on their respective pages.
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 issues persist, please open a new support ticket at WPML support forum.
Problem: The client created a variable product in WooCommerce and needs to translate the name of the default variation. After translating, the product appears empty in the frontend. Solution: 1. Ensure the WooCommerce Multilingual & Multi Currency plugin is installed and activated. You can download it from here. 2. Edit the variable product in the default language ensuring that the "WPML Translation Editor" is enabled. 3. Translate the secondary language product using the WPML Translation Editor. For detailed steps, refer to this documentation. 4. If the variation still does not show in the frontend, follow these troubleshooting steps: - Clear the cache in WPML. - Synchronize posts taxonomies. - Remove ghost entries from the translation tables. - More steps can be found in the WPML Support Troubleshooting page. 5. Consider creating global attributes and translate them either during the product translation or via WooCommerce >> WooCommerce Multilingual & Multicurrency > Attributes tab.
If these steps do not resolve the issue, 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 the problem persists, please open a new support ticket.
Problem: The client was unable to open the Elementor editor for a translated page/template, resulting in a 403 Forbidden error and an uncaught TypeError. Solution: The client said he had found a folder named /he/ on the server. Removing this folder solved the problem. If this solution is 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. If issues persist, please open a new support ticket at WPML support forum.
Problem: The client is experiencing an issue where the currency switcher does not affect the currencies displayed in sidebar widgets on the homepage, despite working correctly on product and category pages. Solution: We recommend deleting the
object-cache
and
advanced-cache
files from the wp-content folder on your staging site. This approach resolved a similar issue on our local test site, suggesting that cached data might be preventing the currency switcher from updating the sidebar widgets correctly.
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, please feel free to open a new support ticket with us for further assistance at WPML support forum.
