On the demo site I created a page called "WPML Test" with the content that causes issues.
You can replicate the issue by doing this:
1. WPML > Translation Management
2. Select the page WPML Test
3. Click on "Add selected content to translation basket"
4. Click on "Translation Basket" after the page reloaded.
Now it works fine in test site: hidden link
We did not do anything.
Could you please check again after updating all your WPML plugins on your site.
If you still see the issue please create a temporary admin user and let us know the username and password in the next private reply.
Thank you for your feedback. Unfortunately, the issue is still persisting, even on your test environment. I recorded a short video showing it. You can access it here (it is unlisted on Youtube and only accessible through this link): hidden link
We found a bug that if we use the word "Lebensmittelverarbeitung" anywhere we see the issue.
Even if you add this to default Gutenberg text block we see the issue.
Our developer team is working for this.
If you do not use the word "Lebensmittelverarbeitung" you can proceed with no issue.
If you still want to use the same word you have to wait for the fix. We will let you know once find it.
I hope you are well. It has been over a month since we both identified the issue and I was wondering if there is a fix for it yet? We are patient but did not expect it to take this long.
Our developers are still working on it and this will be included in future updates.
We do not have ETA yet for this.
This is a rare case.
I will update you soon once this is included in the updates.
I hope you are well. Today marks 3 months since we brought up the issue. There still has not been an update to fix this. I really do not want to sound pushy, but I expected more given that the license comes with "Support".
Without being able to translate this page, we are stuck and eventually forced to use another plugin (which is crazy, given that we have translated everything else with WPML).
I know you said that you do not provide an ETA on updates, but would it be possible to involve one of the developers in this topic and perhaps get a temporary fix without an official update?
