Problem: The client reported issues with automatic translations not detecting HTML fields in product category descriptions and some descriptions not being translated at all. Additionally, there were problems with the HTML structure not being respected in translations, which is crucial for SEO, and issues with Yoast SEO term meta not appearing translated in the frontend.
Solution: 1. To address the HTML tags issue in product category descriptions: - Edit the file
- In WPML settings, disable the option "Don't show translated taxonomies in Translation Editor" to allow translation of category descriptions directly in the Advanced Translation Editor and retranslate the products. 2. Alternatively, translate the product category manually via WPML > Taxonomy Translation. 3. For translating Yoast SEO term meta, ensure to send the term meta for translation from WPML > Translation Dashboard as detailed in our documentation here. 4. To resolve issues with the same slug across languages, enable the option "Adjust IDs for multilingual functionality" in WPML > Languages > Section Make themes work multilingual.
If these solutions do not resolve your issue or seem outdated, 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. For further assistance, please visit our support forum at WPML support forum.
Problem: The client needs help configuring WPML so that automatic translations run continuously in the background, without requiring them to log into the WordPress admin. Currently, translations only process when logged into the WordPress admin. Solution: 1. Disable WordPress's built-in
wp_cron
: Add the following line to your
wp-config.php
file, ideally just above the
/* That's all, stop editing! Happy publishing. */
line:
define('DISABLE_WP_CRON', true);
This stops
wp_cron
from being triggered by regular site visits. 2. Set up a server-side cron job: Access your hosting control panel to create a new cron job. The command to run
with your actual website's URL. Set this cron job to run frequently, for example, every 5 or 10 minutes. Note: There are no specific WPML hooks or WP-CLI commands designed to directly trigger or force automatic translation processing independently of the general
wp_cron
system. The server-side cron job approach is the most reliable method for ensuring all WordPress and WPML background tasks, including automatic translations, run consistently.
If this solution does not resolve your issue, or if it seems 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client suggested integrating ChatGPT as a new automatic translation tool in WPML to improve translation accuracy compared to other tools like Deepl. Solution: We recommended trying our WPML AI Engine called PTC, which is a hybrid engine combining AI technologies and in-house techniques to enhance translation quality. This engine is specifically fine-tuned for each language pair, curated by linguists and developers, and continuously tested to ensure superior control over translation outputs. Although it is more expensive, the enhanced quality justifies the cost. We encourage you to test the PTC engine and share your feedback with us.
If this solution does not fully address your issue or seems outdated, please check the related known issues, verify the version of the permanent fix, and ensure you have installed the latest versions of themes and plugins. If further assistance is needed, we highly recommend opening a new support ticket or visiting the WPML support forum.
Problem: The client needs a shortcode [sc name="echr"][/sc] to be automatically translatable in the Advanced Translation Editor (ATE) without having to search for it each time, especially when used in page titles. Solution: We explained that the Advanced Translation Editor by default does not display non-visual elements like HTML attributes or shortcodes directly. However, once these shortcode attributes are translated in ATE, they are saved in the translation memory. This means that they do not need to be translated again unless the original content changes. For more details on how ATE handles translations, you can visit the documentation on the main features of the Advanced Translation Editor at ATE Feature.
If this solution does not fully address your issue or seems outdated, we recommend opening a new support ticket. We also advise 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: You want to translate the code of some widgets in Elementor to display the widget, fields, and buttons in different languages. This was possible in the Classic Translation Editor but not in the new Advanced Translation Editor (ATE). Solution: Currently, the functionality to translate widget code directly in ATE is not supported. We have escalated your feature request to our development and management teams for consideration in future updates. We appreciate your feedback as it helps us prioritize improvements.
If this solution does not apply to your case, or if it becomes 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 contact us through the WPML support forum.
Este código debe añadirse al archivo functions.php de tu tema hijo. Además, estamos considerando ajustar este comportamiento en futuras versiones de WPML para evitar problemas similares.
Si esta solución no resuelve tu problema o si la información proporcionada se ha vuelto obsoleta, te recomendamos revisar los problemas conocidos y verificar que tienes instaladas las últimas versiones de los temas y plugins. Si el problema persiste, no dudes en abrir un nuevo ticket de soporte. Estamos aquí para ayudarte.
