[Resolved] Translated taxonomies are not used in the automatic translation
This thread is resolved. Here is a description of the problem and solution.
Problem: You are using WPML with the WP Recipe Maker plugin on your recipe website and have translated taxonomies like 'Ingredient Unit' from English to German. However, when using automatic translations for recipes, some taxonomy terms such as 'tsp' to 'Esslöffel' are not correctly translated in the recipes, displaying the original term instead.
Solution: The issue arises because the WP Recipe Maker plugin stores ingredients and units as strings in the post meta (custom fields) rather than using taxonomy terms directly. To resolve this, you should: 1. Add the ingredient terms to the WPML glossary using the Advanced Translation Editor. This ensures consistent translation across your recipes. Learn more about managing glossary entries here: WPML Glossary Management. 2. Alternatively, you can manually link the custom field values to the translated taxonomy terms using the
get_term_by('slug' or 'name')
function and the wpml_object_id filter to display the correct translated term.
Please note that the solution might be irrelevant if it's outdated or not applicable to your specific case. If these steps do not resolve your issue, we highly recommend checking related known issues at WPML 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 with us for further assistance.
This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
Background of the issue:
I have translated all taxonomies from English to German for my recipe website using the WP plugin Recipe Maker. I use the custom post type 'recipe' to showcase recipes. With automatic translation, I've translated some of these recipes. The problem is that some of the taxonomies translated before are not used in the automatic translations.
All relevant content, including post types and taxonomies, is set to be translatable. WPML, WP Recipe Maker, and the GeneratePress theme are all updated to the latest versions.
Symptoms:
For example, the taxonomy 'Ingredient Unit' includes the term 'tsp' that I've translated and saved as 'Esslöffel' in German in taxonomy translations. Automatic translations of recipes still display 'tsp' instead of 'Esslöffel.' Similarly, the term 'Wraps' in the 'Ingredient' taxonomy translates to 'gewickelt' inconsistently in recipes. It should be "Wraps", the term that I've saved for the German translation.
Questions:
Could you please assist me in resolving this issue?
Welcome to WPML support. I will answer this ticket before the ticket is assigned to one of my colleagues.
Would you please make sure you followed the steps mentioend in the documentation below?
hidden link
If yes, can you test for one recipe and see if the steps below fixes the taxonomy translation issue?
- Go to your Dashboard > Pages.
- Open the edit screen of the original page. You should see a pencil/circle/gear icon in the sidebar options under the "Languages" section.
- Make a small change, for example, add an extra blank space at the end of a sentence/paragraph.
- Save it.
- You should now see that a circular arrow appears beside the 2nd languages links, this means that an update is required.
- Edit the translation again and save it up to 100% translated.
Yes thanks for the fast reply.
I've tried this but it's not working. This is affecting the posts but not the recipes.
I've tried it after adding translated recipes to posts as well but then it's not changing the recipe meta data as desired.
Could you please grant me access to your site and explain how and where I can view the issue?
If you require additional assistance with this, please share the access details to your site with me. I'm enabling a private message for the following reply.
Privacy and Security Policy
We have strict policies regarding privacy and access to your information. Please see: https://wpml.org/purchase/support-policy/privacy-and-security-when-providing-debug-information-for-support/ **IMPORTANT**
- - Please backup the site files and database before providing us access. --
-- If you have a staging site where the problem can be reproduced, it is better to share access to the staging site.--
Thanks for sharing the correct password. It works, and I can access your site. However, and very important, please know that you have shared it in a public reply. I'm unsure why you have ignored the private reply. (Not filling in the access details fields causes the reply to be public.) Important!
Our forum is public. It is not a private discussion or thread between you and us. So, please refrain from posting sensitive information in public replies. I have hidden your previous reply with the login details. For the safety of your site, please update the password.
I'm now checking the issue on your site and will get back to you.
I'm also using Chrome and could just now edit the private reply. I'm unsure what goes wrong when you try. Maybe you should try it with another browser.
In any case, I'm again enabling a private reply for the following message. Please ensure that you add the access details to the designated fields and check the corresponding checkboxes. It should look like this. Please see the attached screenshot.
I checked things on your site. To the best of my understanding, it is about translating fields in the German recipe. I'm uncertain if it's about translating the Ingredient Units. I edited the German recipe here: hidden link. I translated "tsp" (I added DE) directly in the field. Please see the attached screenshot, edit-recipe.jpg. Then I checked the German recipe post and could see that my translation displays. Please see the attached screenshot translation-on-frontend.jpg.
But I want to use the taxonomies that I have already translated. This is very important for me because I need a standardised wording so that the search filters work. If, for example, "tsp" is translated as "tablespoon" in one recipe and "tsp-DE" in another, what is the point of translating the taxonomies at all?
In some cases, the translated terms from the taxonomy translations are simply not used in the automatic translation.
If I have to translate everything manually anyway to make sure the wording is consistent, then that's a lot of effort and really disappointing considering the price of WPML compared to other language plugins...
Yes, I get your point, but I was wondering if those fields are actually holding the taxonomies. I'm unsure about it. The WP Recipe Maker plugin has some out-of-the-ordinary ways to implement things. The authors of the plugin were responsible for the guide on working with WPML. In their guide, they wrote this: "Our recommendation for using WP Recipe Maker on a multilingual blog is to create a separate recipe for separate languages. If that’s not an option for your site, the WPML Automatic Translation should work reasonably well." I wonder why they mention that it should work "reasonably" well... Did they mean that in certain cases it will not work well...
Maybe we are facing here a compatibility issue that has not been reported yet. Therefore, we need to replicate this issue on a fresh WordPress installation. Then I'll be able to escalate it to our compatibility team. To achieve this, I created a test website with a clean WordPress installation. You can access it through this link:
hidden link
With this link, you'll be directly logged in.
Could you please install the WP Recipe Maker plugin and see if the issue is replicable on a clean WordPress installation?
I already configured WPML to have English as the default language and German as the second language. There are 2000 automatic translation credits assigned to this test page.
Please also make sure that you are installing the latest version of the plugin.
When everything is finished and you can replicate the problem, please let us know. And please describe the exact steps you took that led to the problem.
Important! Do not import your site to the test site. We must replicate the problem on a fresh, clean WordPress installation.
Thank you for providing the sandbox environment.
I've replicated the problem with the following steps:
1. Set respective taxonomies to translatable
2. Create test taxonomy terms "tsp" for ingredient unit and "Wraps" for ingredient in WP recipe Maker
3. Translate these terms in taxonomy translation
4. Create English "Dummy" recipe with these values
5. translated "Dummy" from English to German with the automatic translation feature.
The translated taxonomy terms were not correctly applied in the automatic translations.
Thanks for replicating the problem on the sandbox site. I'll check it and escalate it to our second-tier supporters team. We will keep you updated on any news regarding this issue.
