Unable to translate Spanish Language

Can you give some more information on the language mappings you did and a screenshot of you tmgmt configuration?

Sure.

The translation workflow is

1. You first locate the page you want to translate and then navigate to the right to the drop-down and choose "translate"
2. Then, you choose which language it should be translated into and click "Request Translation."
3. Then you can put a name to the translation request and have to select "DeepL API Pro" under the Provider setting and then click "Submit to Provider."
4. It will then instantaneously translate the page. But it needs to be approved first. To approve the job, you have to navigate to
https://utimaco.com/admin/tmgmt/jobs, locate the page, and then click on "Manage" under "Operations"
5. If you then click on "View," you will enter the editor where you can make adjustments to the translated page if necessary, and then down below, click on "Save."

tmgmt_deepl_glossary - Version - 2.2.2
The Version of tmgmt_deepl - Version - 2.2.2.

Thanks,

@divya.pm
Have you tried using the latest version of the module ?
Do you use the tmgmt_deepl_glossary module and have you resynced glossaries?

I'm aware of the translation workflow, since i wrote the module ;) ..

@steffenr
I have updated to the latest version, 2.2.7. When I create the EN page, it automatically translates to ES without requiring me to select the "Request Translation" button. Is there any configuration required?

Do you use the tmgmt_deepl_glossary module and have you resynced glossaries? =>No I have not resynced, Should I click the "Sync DeepL Glossaries" button on admin/tmgmt/deepl_glossaries?

Thx

When I create the EN page, it automatically translates to ES without requiring me to select the "Request Translation" button. Is there any configuration required?

This is not an tmgmt_deepl related issues - sounds like you have configured a continous translation job within your tmgmt configuration.

No I have not resynced, Should I click the "Sync DeepL Glossaries" button on admin/tmgmt/deepl_glossaries ?

In cases of using a glossary on multiple instances (e.g. staging, production) we had the issue, that non existing glossaries led to 404 errors while translating. But this can be fixed by simply syncing the glossaries.

@steffenr

We have upgraded the module to the latest version on the Staging site, where it works and automatically translates to Spanish. However, after upgrading the module on the Live site, it is not working, and I have been facing this issue.

Drupal\tmgmt\TMGMTException: DeepL API service returned the following error: Not Found in Drupal\tmgmt_deepl\Plugin\tmgmt\Translator\DeeplTranslator::doRequest() (line 399 of /usr/www/users/utimai/web/modules/contrib/tmgmt_deepl/src/Plugin/tmgmt/Translator/DeeplTranslator.php).

@harishwar r
Do you have a glossary for the language - e.g. english -> spanish?
Have you re-synced the glossaries on prod?
I already mentioned, that this could be related to glossaries, you are using on stage and production. In case of changing entries on stage and saving those, you get inconsistencies and previously used glossary_ids on prod won't work.

For further investigation, i need more steps to reproduce the issue. Since it's working on you staging system, the module is working fine.

But for your internal investigastion/ debugging i would suggest the following steps.

• get a latest database dump from production, where the error exists
• try to reproduce the error on your local environment
• use a debugger to check the query send to the deepL API
  • use postman or equal tools to check for existence of glossaries by running API calls against the glossary endpoint
  • use postman and rebuild the original query and run the API calls against the translate endpoint

Further info on API usage, can be found here: https://developers.deepl.com/docs