Add Exception handling

[MajPay]

When the DeeplTranslationService is constructed it may throw an exception when something is wrong with deepl or the apikey (quota limit for example). In that case an error message should be rendered. In the moment the exception is thrown and the backend is no longer usable.

[dmitryd]

Please, provide a full stack trace.

[MajPay]

Really? Its enough to configure a wrong api key.

Simply include the typoscript and add the following constant:

module.tx_dddeepl.settings.apiKey = invalid-key

From now on it's impossible to fix this from the backend, you can not open any module with a page-tree. The same happens if your quota is exhausted.

A DeepL\AuthorizationException exception is thrown by /vendor/deeplcom/deepl-php/src/Translator.php and won't be handled by Dmitryd\DdDeepl\Service\DeeplTranslationService in the constructor.

[MajPay]

you can not open any module with a page-tree

So in case you added a wrong api key, you wont be able to fix this without using raw SQL or uninstalling deepl, removing the wrong key, installing it again... So IMO this is pretty severe

[dmitryd]

Preferred method to set the API key is via environment. I will check. I think it is already solved in the recent version.

[MajPay]

I need to add different keys for different sites, so i used the constants.

[saitho]

Is this still happening in the latest version? We're trying the extension with a free key for now.
Would be bad if the backend was unusable, if the quota is reached. :)