[BUG] Target Language (ISO Code) [deeplTargetLanguage] is empty

[medarob]

Describe the bug
We have installed the extension for the first time. In the site config we noticed that the Target Language (ISO Code)[deeplTargetLanguage] field is empty in the ENGLISCH and GERMAN site configuration.
The site has just two languages: German and English

We couldn't find anything in the documentation about configuring it and as we unserstand it, the values in the dropdown should be picked up automatically?

What have we missed?

Screenshots
German [ID 0]

ENGLISCH [ID 1]

TYPO3 Setup

• TYPO3 Version: 11.5.41
• Server: Apache/2.4.6 () OpenSSL/1.0.2k-fips
• Database type and version: MySQL 10.4.34-MariaDB
• PHP version 8.2.20
• DeepL free or paid API? Free
• composer or classic setup? composer

[calien666]

@medarob This should mean, you don't have the API key set up correct.

Please take a look at https://docs.typo3.org/p/web-vision/wv_deepltranslate/draft/en-us/Reference/ExtensionConfiguration/Index.html

[medarob]

Mh, the API key was added before:

The two options to translate the elements are available but don't translate any text:

[calien666]

Okay, seems, that your cache is broken, if the key is valid. Please go to your server and delete the files located in var/cache/data/wvdeepltranslate, as sometimes they are created empty, which should not happen, but in some cases, we couldn't detect, happens.

[medarob]

I delete the two files, no change.
I installed the main-branch because there was a proxy fix included and we have a proxy, cleared all caches but still no change.

  - Upgrading typo3/class-alias-loader (v1.1.4 => v1.2.0): Extracting archive
  - Upgrading guzzlehttp/promises (2.0.3 => 2.0.4): Extracting archive
  - Downgrading deeplcom/deepl-php (v1.9.0 => v1.8.0): Extracting archive
  - Upgrading web-vision/wv_deepltranslate (4.3.1 => dev-main d82b991): Extracting archive

The package deeplcom/deepl-php was downgraded, all other packages where updated. No sure if that is correct?

The content of wv-deepl-supported-languages-source/target is just a:0:{}.

The configuration settings have changed and the field Deepl Formality is now not available anymore.

[medarob]

Is there a way to find out if the connection to Deepl works in general? Something like a status icon which shows if a connection to Deepl could be established or not.

[calien666]

The downgrade of deeplcom/deepl-php is correct, as we currently work with the older code and have to fix for the latest deepl-php.

Formality is now gone to SiteConfiguration and no longer part of the extension settings, as you are now able to define formality per language and no longer for the complete system.

If your connection to DeepL API is correct, should be simply tested by calling the deepl:glossary:list command. If the connection doesn't work properly, you should get an error there.

[medarob]

The TYPO3 error log shows the following:
[ERROR] request="3c5629b5ceb99" component="WebVision.WvDeepltranslate.Client": Failed connect to api-free.deepl.com:443; No route to host (7)

So, the connection to Deepl doesn't work I would think. Maybe it has something to do with the proxy settings but not sure what I have to change here...

Just a side note:
Maybe a feature could be added with a status text that the connection to Deepl is OK/Not OK.

[h-e-l-l-o-w-o-r-l-d]

Same here. Digged deeper into it and found out that there are several problems with your implementation of getting the proxy setting:

• You should not use GeneralUtility::isValidUrl(), as it returns NULL if there's no protocol. As proxy settings are usualy set without protocol (see TYPO3 Docs), it always returns NULL in that case.
• You don't respect $GLOBALS['TYPO3_CONF_VARS']['HTTP']['proxy']['no']
• You don't respect $GLOBALS['TYPO3_CONF_VARS']['HTTP']['proxy']['https']

The first point is the cause for this issue, the others should be respected, too.

See dd_deepl for a perfectly working implementation. ;-)

[calien666]

We will take a look into the proxy settings and configurations, adjusting the code, fitting all requirements. Thank you for reporting.

[h-e-l-l-o-w-o-r-l-d]

Thank you!

[Mabahe]

Hey, had an issue related to this and have already a patch. Will push a PR in a minute.

[Mabahe]

Pushed. If anybody want to test based on the latest release here is the commit for 4.3.1:
Mabahe@86401f1

[Mabahe]

finally... :-)

[mschwemer]

We had the same issue with a client setup.

I can confirm the PR works here too.