Problem: If you're trying to enable automatic translations but want to exclude certain posts in specific categories, you might be facing some difficulties.
Solution: We recommend using the "Translate what you choose" mode, which allows you to manually create translation jobs from WPML > Translation Management > Dashboard. This mode gives you the flexibility to send content for automatic translation or assign it to local translators as needed.
However, if you prefer to use the "Translate everything automatically" mode and still want to exclude specific posts from automatic translation, you'll need to edit each original post in the WordPress Editor. In the right sidebar, change the translation method from "WPML Translation Editor" to "WordPress Editor". This action will exclude those posts from automatic translation.
Please note that the solution provided might be outdated or not applicable to your case. If the issue persists, we highly recommend checking the related 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, don't hesitate to open a new support ticket with us.
Problem:
The client uses the legacy Views editor to create a View to display taxonomy terms.
The texts from the View are translated via String Translation, but on the translated page the View query returns no results, unlike in the default language where all of the taxonomy terms are shown.
Solution:
The problem was that the output of the View is ordered by a taxonomy custom field, and in WPML settings that term field is set as Do not translate. That means that in the secondary language the terms have no values for that custom term field.
It is a quirk of WordPress that when ordering by some thing, and potential results that have no value for that thing will be excluded from the results.
The solution is to copy or translate the custom term fields.
Problem: The client was experiencing an issue where a Toolset shortcode inside a block was not correctly inserting the URL from a Toolset field in the translated version of the page.
Solution: We checked the Spanish template and edited it to ensure the button URL matched the English template. If you're experiencing a similar issue, we recommend checking the translated template and making sure the URL is correctly inserted from the Toolset field.
