Problem: The client is unable to translate products using WPML due to a persistent 'processing' status and an error indicating a call to an undefined function
get_current_screen()
within the Easy Subscriptions plugin. Solution: We recommend contacting the support team for the Easy Subscriptions plugin to address the undefined function error. If they cannot resolve the issue, consider switching to an alternative plugin that is compatible with WPML. You can find a list of compatible WooCommerce extensions here: https://wpml.org/plugin-functionality/woocommerce-extension/ For issues related to translating Gravity Forms, ensure that the forms are translated into the secondary languages following this guide: https://wpml.org/documentation/related-projects/gravity-forms-multilingual/ If problems persist, please open a new support ticket with detailed information.
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, do not hesitate to open a new support ticket for further assistance.
Problem: The client needed editors to access more WPML features, specifically the glossary function, without elevating them to Translation Managers. Despite being registered as translators, editors were unable to access or modify the glossary. Solution: We clarified that by default, editors do not have access to all WPML features. To allow editors to translate content, they must be added as translators via WPML->Translation Dashboard->Manage Translators & Services, which the client had already done. This setup enables editors to translate assigned content or initiate translations directly from pages or posts. However, for editors to access and manage the glossary, they must be assigned as Translation Managers. This role will allow them to update, add, or remove glossary items. The glossary itself automatically applies during translations in the Advanced Translation Editor, providing accuracy and context without direct editor intervention. For more details on managing glossary entries, visit How to Create and Manage Glossary Entries.
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 at WPML support forum.
Problema: El cliente tiene el tema Proty instalado y aunque traduce el apartado de header en el front, siempre aparece en español. Solución: Primero, es importante verificar si el problema persiste incluso sin WPML activado, ya que Elementor y WPML requieren más de 128M de memoria para operar correctamente. Sigue estos pasos: 1) Desactiva WPML. 2) Abre la página de inicio original en Elementor. Si la página no carga y aparece un error en la consola del navegador, el problema está en Elementor y no en las traducciones. En este caso, debes contactar al equipo de Elementor para resolver este problema. Una vez resuelto, las traducciones deberían funcionar correctamente.
Si el problema persiste después de seguir estos pasos, 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. Si necesitas más ayuda, no dudes en contactarnos en nuestro foro de soporte.
Problem: The client is experiencing a timeout error in the backend while editing a page using the Divi builder. This issue persists even when WPML is disabled, suggesting that WPML is not the cause of the problem. Solution: 1. Test the backend editor with WPML disabled to confirm if the issue continues. 2. If the problem persists with WPML disabled, it is likely related to the Divi Builder or a conflict with other plugins. In this case, we recommend contacting Divi support for further assistance. 3. If you suspect that WPML might still be involved, or if specific issues appear only when WPML is active, please let us know, and we will investigate further.
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: The client is trying to remove the padding-right on the language switcher in the top menu on the right but is unable to target the switcher properly or override the properties due to multiple !important tags. Solution: 1. The issue might be related to the CSS from WordPress itself, specifically from the Gutenberg block styles. The padding might be set by the following CSS rule in the file
2. If the issue persists, it might be due to the theme. We recommend testing with a different theme, such as the Twenty Twenty Five Theme, to see if the issue still occurs. You can use a WPML test site to experiment with different themes and settings.
3. Additionally, the padding issue might be influenced by CSS Flexbox properties set in the class
.wp-block-navigation__container
from the file
/wp-includes/blocks/navigation/style.css
, which uses
display: flex;
.
If these solutions do not resolve the issue or 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. If the problem persists, please open a new support ticket.
