As shown in the screenshot, I attempted to translate the popup manually. However, when I click in the input box, the German content is automatically inserted, as it already exists in German. Ideally, it should translate into English.
Based on this behavior, it seems risky to proceed with bulk translation, as the credits may be consumed translating content into German instead of English. Our requirement is to translate from German to English.
Could you please check and guide us on how to ensure the correct translation direction?
The German content you see is coming from Translation Memory. This means that this segment was already translated before and is being reused now, because someone already added translation like that.
You are not charged again for these segments.
You can either manually adjust the translation to English, or
click “Translate automatically” and WPML will fill the remaining content with automatic translation (only new segments will consume credits)
Once saved, those translations will also be stored in memory and reused in the future without additional cost.
Hope this helps clarify things, let me know if any questions.
This is a new post that was created earlier in German and was not previously available in English or translated by anyone. While we understand there may be compatibility considerations with the Rentman plugin for products and categories, translations for default posts and pages should ideally work. However, they are not functioning correctly at the moment.
We need to resolve this urgently, as the site is going live in the coming days. Additionally, translation credits have already been spent, so we cannot risk repeated testing, as it will continue to consume credits without guaranteed results.
Could you please check this at the earliest and guide us on the correct approach to resolve the issue?
Looking forward to your support.
New threads created by Dražen and linked to this one are listed below:
To keep things clear and avoid confusion, let’s focus on one issue at a time. I have opened a new ticket specifically for this translation issue so we can investigate it properly there.
