Skip to content Skip to sidebar

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.

Tagged: 

This topic contains 32 replies, has 1 voice.

Last updated by Itamar 9 months ago.

Assisted by: Itamar.

Author Posts
July 29, 2025 at 7:17 pm #17280147

maximilianK-25

Hi Itamar,

Thank you for sharing this approach and reaching out to WP recipe maker.

However, I'm not sure if that will work, so I'll fall back on the “semi-automatic” glossary approach. I can't tell you how many credits I've lost so far, but I need about 500,000 credits.

Thank you in advance,
Max

July 29, 2025 at 8:16 pm #17280288

Itamar
WPML Supporter since 02/2016

Languages: Hebrew (עברית )

Timezone: Asia/Jerusalem (GMT+03:00)

Hi, Max.

That's for updating me on the approach you decided to take.

Regarding the automatic translation credits. As I mentioned, you have used 90,348 automatic translation credits on hidden link. 500,000 is more than 5 times what you have used. I'm sorry, but we can't compensate you with such a significant number of credits. Out of goodwill, we've added 10,000 credits to your site. You should now see that you have 11,808 credits.

We will keep you updated on news regarding the issue of this ticket.

Regards,
Itamar.

August 4, 2025 at 12:24 pm #17293029

Itamar
WPML Supporter since 02/2016

Languages: Hebrew (עברית )

Timezone: Asia/Jerusalem (GMT+03:00)

Hi,

I'm sorry, but we probably do not have the best news for you coming from the authors of the WP Recipe Maker plugin. They decided not to proceed with the fix we suggested to them. They wrote the following to our compatibility team.

The problem here is that it would suddenly require a lot more database calls, as it needs to retrieve the term for every single ingredient and unit, which would have an impact on performance. The vast majority of our users are not using WPML, so this feels like a bad trade-off.

I must say that from their perspective and the way their plugin is coded, they are probably right with this decision as it will cause significant performance problems for clients who do use both plugins.

I'm closing this ticket as we have exhausted all possibilities to help with this case.

Thanks for your understanding,
Itamar.