Problem: El cliente experimenta que el backend de WooCommerce y parte de WPML están en inglés en lugar de español, su idioma por defecto. Este problema ocurre cuando ciertos plugins de WPML están activados. Solution: Primero, asegúrate de que todas las traducciones y actualizaciones estén completas, especialmente para WooCommerce. En WPML, ve a Localización de temas y plugins y desactiva la opción
Automatically load the theme's .mo file using 'load_textdomain'
. Guarda los cambios y refresca tu navegador. Además, verifica la configuración de idioma en Settings -> General y ajusta el idioma del backend si es necesario. Si los problemas persisten o si notas que la Rest API aparece como desactivada (un falso positivo común), intenta desactivar y reactivar los plugins de WPML para ver si el mensaje desaparece.
Si esta solución no resuelve tu problema o si parece estar desactualizada, te recomendamos abrir un nuevo ticket de soporte. También es aconsejable revisar los problemas conocidos y asegurarte de que tienes instaladas las últimas versiones de los temas y plugins. Para asistencia adicional, visita nuestro foro de soporte.
Problem: The client is developing a site using Beaver Builder and WPML and has encountered an issue where the same logo displays for both the Spanish and English versions of the site, despite using the WPML media plugin for translation. Solution: If you're experiencing this issue, we recommend checking if you have added the logo via theme options and then translating the logo image via String Translation. For detailed guidance, please refer to the following documentation and forum topics:
If this solution does not resolve your issue or seems outdated, 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 you still need assistance, please open a new support ticket at WPML Support Forum.
Problem: The client is unable to translate the 'Before' and 'After' texts in the advanced fields of the icon list items created with Elementor and connected to an ACF dynamic attribute. Despite the fields being translated and updated, these specific texts do not appear in the Advanced Translation Editor. Solution: We first recommended ensuring that all WPML plugins are updated to the latest version and provided guidance on translating Elementor templates, which can be found here: https://wpml.org/documentation/plugins-compatibility/elementor/#translate-elementor-templates. Upon further investigation, it was discovered that the dynamic field functionality is provided by the 'PRO Elements' plugin, which is not officially compatible with WPML. The data for these fields is stored in a format that requires specific implementation by the plugin author to be recognized by WPML's translation editor. We suggested reaching out to the PRO Elements plugin developers to request compatibility or consider using the official Elementor Pro plugin for better integration. Alternatively, manual translation of these fields or hiring a developer for custom coding were recommended as immediate solutions.
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 at WPML support forum.
Problem: You have installed a plugin to translate your German website into English, but the product category is missing on the English translation page. Solution: We recommend checking the English language portfolios to see if the custom field "id_field" exists. This issue might be due to the "Order By" custom field condition not working correctly on the English language page. If the field is missing, adding it 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 issue persists, please open a new support ticket.
Problem: The client is using WPML to translate their website but encounters issues with missing translations in certain sections. Translations only appear correctly when the 'Look for strings while pages are rendered' option is enabled. Disabling this option causes translations to revert to their original state. The client has tried clearing the WPML cache and syncing links without success. Solution: We suggest that this might not be a WPML issue but rather related to changes in how WordPress 6.7 handles language files and translations, particularly with WooCommerce. Here are the steps we recommend: 1. Review the developer advisory on translation loading changes in WordPress 6.7 at https://developer.woocommerce.com/2024/11/11/developer-advisory-translation-loading-changes-in-wordpress-6-7/ 2. Consider rolling back to an earlier version of WordPress as a temporary workaround. 3. Disable WPML and its addons to confirm if the issue persists, indicating it might not be related to WPML. 4. Check if the issue is resolved in the latest WordPress update 7.6.1. 5. If problems continue, contact the Woodmart support team for further assistance.
If these steps do not resolve your issue or if the solution seems outdated or irrelevant, 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.
Problem: If you're experiencing issues where all translations are missing after reverting your website to a previous date, and you're concerned about losing translations for which you've already paid. Solution: First, we recommend checking the translation memory where all translations are stored. You can retrieve your previous translations from there without incurring additional costs. Follow the steps in this screen recording: https://go.screenpal.com/watch/cZXFfInVquM to add the translations back to your pages. Additionally, you can initiate an automatic translation process for all pages; rest assured, you will not be charged again for translations that have already been paid for and are stored in the translation memory.
Please note that this solution might be irrelevant if it's 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 the issue persists, please open a new support ticket at WPML support forum for further assistance.
Problem: The client is experiencing issues with a 3rd party plugin widget not translating correctly. Specifically, the titles on product filters and the 'Search Products...' placeholder are not appearing in the correct language. Additionally, the client mentioned that posts set to publish when the original is published are being published prematurely. Solution: For the translation issues with the widget, we recommend duplicating the category filter and assigning the appropriate language to each duplicate. This method should help ensure that the widget displays correctly in each language. For the issue of posts being published prematurely, ensure that the 'Publish the translated post when the original is also published' option is correctly configured to match your scheduling needs.
If these solutions do not resolve your issues or if they seem 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 further assistance be needed, please do not hesitate to open a new support ticket at WPML support forum.
