Problem: You are working on a site and notice that some translated content is not visible in the Advanced Translation Editor (ATE) of WPML, appearing as empty boxes, although it is visible in the Classic Translation Editor (CTE). Solution: If you switch to the ATE, translations done previously in the CTE will not appear in the ATE. These translations will still display correctly on the front-end of your site. To reuse existing translations, you can manually copy them from the front-end or use the Translate automatically option within the ATE to quickly re-translate the content. For more details, visit https://wpml.org/documentation/automatic-translation/.
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 for further assistance.
Problem: You are managing translations using WPML and have noticed that existing users are not visible in the Translators section of Translation Management. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Open your database and navigate to the wp_options table. 2. Locate the
wpml-cache-translators-translate
option and remove it. 3. Return to your site and re-add the translators. WPML will rebuild the cache automatically. Please ensure that you back up your database before making any changes.
This solution might be irrelevant if it's 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 the issue persists, please open a new support ticket at WPML support forum.
Problem: After updating to WPML 4.7.4 and String Translation 3.3.3, issues arose with post categories not being recognized correctly on the front end when using Elementor. Disabling String Translation temporarily resolved the issue, indicating a compatibility problem between the updated versions of WPML, String Translation, and Elementor. Solution: We identified that the issue stems from Elementor using
term_taxonomy_id
instead of
term_id
, which our code did not anticipate, leading to all results being shown without filtering by a taxonomy term. A fix for this issue will be included in the upcoming WPML 4.7.5 release. Meanwhile, we provided a workaround involving a code modification in
. This modification should be tested on a staging site after taking a full backup. If this solution does not resolve your issue or seems outdated, please check for related known issues at https://wpml.org/known-issues/, verify you have the latest versions of themes and plugins, and if necessary, open a new support ticket at WPML support forum.
