Problem: The client is trying to translate media meta fields using JetEngine with WPML. They want to enable translations for captions within the translation editor rather than separately in WPML > Media Translation. Issues were reported where images and captions were not visible in the translation editor for certain languages, and in some cases, translated captions in image sliders were displayed in the default language instead of the translated language. Solution: 1. Enable the "Translate media library texts with posts" option in WPML → Settings. This setting helps synchronize the translation of media texts with their associated posts. 2. After enabling this setting, make minor edits to the affected pages/posts and then retranslate them. This should allow the meta information to appear correctly in the Advanced Translation Editor. 3. For the specific issue of translated captions not displaying in image sliders, we have split the ticket to address this separately. You can follow the progress and find solutions on this issue here: WPML support forum.
If these steps do not resolve your issues, or if the solution seems outdated or not applicable to your case, we recommend opening a new support ticket. Additionally, 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.
Problema: Si estás experimentando problemas para traducir enlaces dentro de las descripciones de productos que apuntan a otros productos, y estos enlaces no se traducen automáticamente al idioma del visitante, es posible que se deba a temas hijos o código personalizado en tu sitio web.
Solución: Para asegurar que los enlaces sean traducibles automáticamente, es importante que el código y la lógica implementados en tu sitio web sigan las pautas y convenciones internacionales, así como los ganchos personalizados que permiten identificar correctamente el contenido como traducible. Te recomendamos revisar y asegurarte de que estás utilizando temas y plugins que son compatibles con WPML, lo cual puedes verificar en las siguientes listas:
Lamentamos que en tu caso, los enlaces no se tradujeran automáticamente.
Si la solución proporcionada no es relevante para tu caso, porque podría estar desactualizada o simplemente no aplicar a tu situación, te sugerimos abrir un nuevo ticket de soporte. Además, te recomendamos encarecidamente revisar los problemas conocidos, verificar la versión de la solución permanente y confirmar que has instalado las últimas versiones de temas y plugins. Si necesitas asistencia adicional, no dudes en contactarnos en el foro de soporte de WPML.
Email strings are mixed when the WooCommerce Order Proposal plugin is active
Solution:
The client reported that the problem came from the third-party plugin WooCommerce Order Proposal. He contacted their support, and this is their reply.
I was also in touch with WP Overnight support (authors 'WooCommerce Order Proposal'). It turned out that the plugin was doing something wrong regarding WPML. The response from support: 'We were reloading textdomains on wpml_language_has_switched hook but also on change_locale, but apparently we don't need to do it on the first.'
I got a modified version of the plugin and this solved the problem. So this ticket can be closed.
Problem: The client was experiencing issues with a custom user role 'Shop Manager' in WooCommerce, which could not edit translations or behave as an editor.
Solution: 1. We identified that this was a known issue and it has been resolved in the latest WPML version. 2. We recommended updating WPML to version 4.6.9, which can be manually downloaded from the client's WPML account. 3. We provided a code snippet that could potentially resolve the issue if the client did not want to update:
4. We also suggested emptying the translation queue by going to the Jobs tab and filtering the jobs. 5. If the client had already added custom code in the theme's functions.php file or added Jac to the translation managers list, we advised removing them after the update.
If this solution does not seem relevant to your situation, please open a new support ticket with us.
