- 🇩🇪Germany SteffenR Germany
Can you share your configuration of the paragraphs field and the widget settings?
Looks like a confguration issue, since the review process/ validation is not part of the tmgmt_deepl itself. The review/ validation is handled via the tmgmt module. tmgmt_deepl "only" provides a plugin to use the possibilities of deepL.
We are using the same combination on one of our clients projects without any problem.
- 🇩🇪Germany SteffenR Germany
@miki_mike & @desch:
Can you give more information on your configuration?
Have you tried another translation service?
Please read my comment above and give steps to reproduce.Thx
Hello @StephenR,
Thank you for your feedback
This is how my field is configured :
Normally, when the "Paragraphs Asymmetric Translation Widgets" module is installed, the error message "(* unsupported) Paragraphs fields do not support translation" is no longer red but yellow, isn't it?
I've just done another test and Deepl does show me the translation of the paragraph fields, but when I save, I don't get the EN values.
Can you show me the configuration of your "paragraph" field with the "Paragraphs Asymmetric Translation Widgets" module and the result of the translation via Deepl?
Thank you in advance.
- 🇩🇪Germany SteffenR Germany
@miki_mike
Sorry for letting you wait for such a long time.
I just tested a similar setup in a D10.2 installation and can reproduce the behaviour. I'll need to spend some time looking a possible causes.
Usually the process of the translator plugin "ends" before adding the translations - this is handled via tmgmt itself.
In the review of translation you can see, that the translated texts are correct, but sth goes wrong while completing the job/ adding the translations to the new node (independent from choosing auto accept or review). - Status changed to Closed: works as designed
9 months ago 3:22pm 5 February 2024