Problem: The client is concerned about translating synonyms from Yoast SEO Premium in WPML's Advanced Translation Editor for better SEO across different languages. Solution: We clarified that the synonyms entered in Yoast's custom fields are used internally for calculating SEO scores and do not appear on the site or influence search engine indexing directly. Therefore, translating these synonyms in WPML will not affect your SEO as they are not visible to search engines. For effective multilingual SEO, focus on translating the main content and key phrases for each language, rather than the synonyms.
If this solution does not resolve your issue or seems outdated, we recommend opening a new support ticket. Also, check the related known issues, verify the version of the permanent fix, and ensure you have installed the latest versions of themes and plugins. For further assistance, please visit our support forum.
Problem: Editor users assigned as Translators are unable to translate content they previously could and receive the message "You can only edit translations assigned to you." This issue arose after recent WPML updates, and attempts to delete Translation Jobs to dissociate translations from any user were unsuccessful. Solution: To resolve this, follow these steps: 1. Edit the file
3. Ensure that the "Manage Options" capability is granted to the relevant users. Note: This change might allow editors to see more admin items. To limit visibility in the admin area, consider using a role/capability plugin like Advanced Access Manager. Be aware that any modifications made directly in WPML plugin files will be overwritten with future updates, so these changes will need to be reapplied after each update. Currently, these changes cannot be implemented via a snippet or hook, and there is no estimated time for when this functionality might be officially supported by WPML.
If this solution does not apply to your case, or if it becomes 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 further assistance is needed, please open a new support ticket at WPML support forum.
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.
