Translation Service

Problem:
The client needed to translate categories and tags for a custom post type called Case Studies on their WordPress site using WPML and BLEND's translation service. Initially, these taxonomies were not set to be translatable, and the client was unsure how to send them to BLEND without resending all the posts.
Solution:
To translate the taxonomies while sending them to a translation service, creating a new post, assigning all categories and tags to it, and then sending it to the translation service. This method allows the categories to be included in the translation when the post is processed. Generally, Taxonomies will be translated using the WPML > Taxonomy Translation option. After translating, you can go to WPML > Support > Troubleshooting and use the first option in the "Clean up" section to synchronize the post taxonomies.

If this solution does not apply to your situation, or if it seems outdated, 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 further assistance is needed, please open a new support ticket.

Problem:
You are using LanguageWire for translations in WPML, and although the connection works and translations are sent and returned correctly, parts of the translated content are missing when loaded in WPML. You are wondering why parts of the translated content are missing and if there is a misconfiguration between WPML and WordPress causing this issue.

Solution:
This is the expected behavior when using translations from a Translation Service like LanguageWire with WPML. If you need to make changes to the translations, you should manually edit them in the WordPress editor. Here are the steps to follow:
1. Send the page for translation to LanguageWire.
2. Once translations are complete, change the original page from WPML Editor to WordPress Editor.
3. Use the WordPress/Elementor editor to open each country page and make changes. This ensures that the translations are no longer linked to the original page and won't be affected by future changes.
Additionally, to prevent the Translation Editor from overwriting your manual changes in Elementor, disable the Translation Editor by following these steps:
- Edit the content in the original language.
- Go to the Language block (usually in the right column).
- Click on WordPress Editor.
- In the Popup window, select the scope of the change.
- Save the changes.

If this solution does not resolve your issue or seems irrelevant due to being 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 problem persists, please open a new support ticket.

Problem:

The client installed the SDL translation service and noticed that when submitting three languages, they appeared as three separate projects in SDL, one for each language.

Solution:

We explained that this is the expected behavior. The integration with SDL is designed to create a separate project for each target language. This is a standard part of the SDL translation workflow. If the client needs more technical details or specific assistance, we recommend contacting SDL support directly.

Please note that 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.