Problem: The client needs to translate custom taxonomy terms ('Resource Type') associated with a custom post type ('Resources'), but these terms are not being translated when sending the resources for translation. Solution:
We suggested the following steps to client and it worked as expected then.
1. Ensure that both the Resources and Resource Type are set as 'Translatable - only show translated items' in WPML>>Settings>>Post Types Translation/Taxonomies Translation. 2. Send the Resources posts for translation to ensure the Resource Type taxonomy terms are also translated. 3. Open an existing Resources post in the WPML Editor and update it to refresh the translation settings. Then, send it for translation again to check if the issue persists. 4. Create a new Resources post and send it for translation as a test to see if there is any difference in the translation outcome.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we highly recommend opening a new support ticket. Also, please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. For further assistance, you can contact us through the WPML support forum.
Problem: The client is unable to send categories and tags to translators using WPML, and documents are not showing up on the translated site. Additionally, titles and notices were not included in the xliff file and thus not translated. Solution: To address the issue of translating categories and tags, we recommend translating the Categories and Tags taxonomy terms manually from WPML>>Taxonomy Translation. Alternatively, create a private post including all the Categories and Tags taxonomy terms, and send that post for translation. For detailed guidance, please refer to our documentation on translating taxonomy terms from a central page and how to translate all taxonomy terms at once.
Please note that the solution provided 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.
Problem: Footer titles and texts were not translated because they were not included in the xliff file. Solution: If you're experiencing this issue, we recommend translating the footer contents via String Translation since they are added through widgets. You can add these strings for translation by navigating to WPML>>String Translation>>Translate texts in admin screens (at the bottom of the screen). After adding, please translate those strings from WPML>>String Translation and check if the translation appears as expected. For more details, refer to the following documentation:
If this solution does not resolve your issue or seems irrelevant due to being 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.
