"tsp" and "Wraps" are actually automatically translated. The Dummy translation engine, activated on the sandbox site, translates the content by prefixing "de" to the translated string. Furthermore, those values are considered custom fields. You can see what I'm referring to in the screenshots you attached in your last reply. The WP Recipe Maker plugin operates in a non-conventional way. I'm consulting our second-tier supporters about this case. I'll update you here once I have their reply.
Our second-tier supporter was unable to reproduce the problem. For him, things work as expected. Here is what he wrote.
1. I installed the package.
2. Following the documentation you provided, I enabled the classic WP UI for taxonomies and enabled the archive for ingredients
3. I translated "Wraps" with "DE Wraps" in WPML > Taxonomy translations.
4. I translated the recipe and reviewed the automatic translation
Results:
5. If I go to the Recipe fields and switch to DE, I can see the ingredient "DE Wraps"
6. If I go to recipes, I'll see both recipes
7. And if I edit the DE one, I can see the ingredient listed
Please see the attached screenshots.
Note: "DE" is just a pseudo translation to test this issue.
Our second-tier supporter followed the guide at hidden link word by word and was unable to replicate the issue.
Our second-tier supporter further suggested and asked the following"
1. Could you please confirm that this is what you were trying to achieve?
2. Perhaps the issue was that the translation wasn't reviewed or published, so the ingredient wasn't published.
3. Perhaps it was due to the classic WP UI for taxonomies, as they explicitly mention it in their "Using WPML Automatic Translation" section.
Could you please see if this information helps you to solve this issue? Maybe you have missed something?
We also recommend you try to get support from WP Recipe Maker. You can show them this thread. Maybe they will be able to figure out what went wrong in your case.
It's not working.
Has the second-tier supporter also tried to translate the ingredient unit "tsp" with "Esslöffel"?
I've tried doing it the exact same way the second-tier supporter has done it. So the classic WP UI for taxonomies and enabled the archive for ingredients and ingredient units are enabled...
Our second-tier supporter has found the reason why this problem happens. He explains the following.
I investigated the issue and found that it is related to how the WP Recipe Maker plugin stores ingredients in the database.
The ingredients (wprm\_ingredient) and ingredient units (wprm\_ingredient\_unit) are handled as taxonomies. When you create a recipe, these terms are used as suggestions that you can select.
However, once the recipe is created, the ingredients and units (wprm\_ingredients) are actually saved as strings in the post meta (custom fields), rather than directly using those taxonomies.
In summary:
- The taxonomies (ingredients and units) are linked to the recipe as reference terms.
- The actual data displayed in the recipe is stored in a custom field (`wprm_ingredients`), which is set as translatable.
Currently, you are translating taxonomies through Taxonomy Translation, while custom fields are translated using ATE (Advanced Translation Editor).
To ensure the ingredient names are translated consistently in the recipes, the recommended solution is to add these ingredient terms to the WPML glossary.
I tested this approach, and it works as expected.
Please read about the Advanced Translation Editor's glossary here.
Hi Itamar,
So with the glossary approach, it works for me now to get the correct terms for the translated taxonomies.
Now I do have a couple of hundred taxonomies that I've already translated with the taxonomy translation feature. Is it possible to import these entries into the glossary?
Will there be any technical issues with that high number of glossary entries?
In the documentation that you've provided it says: "Add Only Critical Terms
Avoid overusing the glossary to define unnecessary terms. Only include terms that both human and AI translators might struggle to translate correctly, such as words with multiple meanings."
2. Edit the exported CSV file and adjust it to match the columns that are required for the CSV file for glossary terms.
You can download a sample glossary terms CSV file from WPML -> Translation Management -> Translation Tools -> Glossary. Please see the attached screenshot.
3. Import the adjusted file in WPML -> Translation Management -> Translation Tools -> Glossary.
Regarding your concern about the content in our documentation, there should be no issue with importing a large number of terms. However, please be aware of the following known issue.
