In the GoogleTranslateService in Line 72 the return type is string. This is wrong an throws an error (Return value must be of type string, array returned).
If the return type is set to array or mixed (the return type of json_decode) it works fine.

The backend user only sees texts for selecting the translate mode in English, even if different language is selected. (For the description, a localized string is used though, just not for the button)

The texts are directly written as strings in Resources/Public/JavaScript/Localization.js and not localized.

Unfortunately, this is the same thing in the core: https://forge.typo3.org/issues/94277

I am not sure, but I think you can use localized strings in the TYPO3 JavaScript API.

TYPO 10.4.31, wv_deepltranslate 2.2.1

When translating content elements (e.g. textmedia) on a page, the last step in the processing progress ("Processing") is not completed. I have to reload the backend and then see the hidden translated content elements.

When selecting several content elements on a page only one content element is translated.

When translating extensions (e.g. news, events2), the translation process is completed correctly and the extension is opened so that I can make any necessary corrections directly.

Free Api uses https://api-free.deepl.com

A hint in the settings section oder the README would be nice.

composer validate

./composer.json is valid, but with a few warnings
See https://getcomposer.org/doc/04-schema.md for details on the schema
License "GPL-2.0+" is a deprecated SPDX license identifier, use "GPL-2.0-or-later" instead

• see https://github.com/TYPO3-Documentation/tea/blob/main/composer.json
• see https://docs.typo3.org/m/typo3/reference-coreapi/master/en-us/ExtensionArchitecture/ComposerJson/Index.html

The translation modes should work with copies, too. Sure, first automatic translation is done 1:1, but it should be possible to add custom elements to translated pages, too.

In my opinion this missing is a major circumstance and it should have been mentioned in the README.md

Your extension works great on TYPO3 v11 with standard content elements, but it seems not to be able to translate content inside flux content elements (https://extensions.typo3.org/extension/flux).

Database-wise this extension adds a field "pi_flexform" which contains the content in an XML-format style:

Is there any chance that content like that will be translateable?

We will drop the support for TYPO3 v9 in the next versions. The TYPO3 v9 LTS Supported has been set for this for a long time and we will follow it here soon.

Deepl 2.2. with glossar function
TYPO3 11.4.14

For example, if I want to translate a news item, I get the error:

Core: Exception handler (WEB): Uncaught TYPO3 Exception: urlencode() expects parameter 1 to be string, null given | TypeError thrown in file /var/www/vhosts/xxxx.my-provider.de/httpdocs/typo3cms/muster/typo3conf/ext/wv_deepltranslate/Classes/Service/DeeplService.php in line 92. Requested URL: https://www.xxxx.my-provider.de/typo3/record/commit?token=--AnonymizedToken--&redirect=%2Ftypo3%2Frecord%2Fedit%3Ftoken%3D--AnonymizedToken--%26justLocalized%3Dtx_news_domain_model_news%253A263%253A1%26returnUrl%3D%252Ftypo3%252Fmodule%252Fweb%252Flist%253Ftoken%253D121ee25112c632739d925cfc0e69eabb633d4a3a%2526id%253D889%2526table%253Dtx_news_domain_model_news%2526pointer%253D1&cmd%5Btx_news_domain_model_news%5D%5B263%5D%5Blocalize%5D=1&cmd[localization][custom][mode]=deepl

and a translation does not take place.
The same applies to other extensions (e.g. events2).

The glossary function works without errors and standard texts are translated.

When translating with deepL, the line break <br> is lost, which can lead to some manual rework.
Regards
Hobokens

TYPO3 10.4.27
wv_deepltranslate - newest version form github

I set up a DeepL API Free Account with Deepl and received an authentication key for the DeepL API.
I entered the authentication key in the extension settings (settings.apiKey (string) and as host 'https://api-free.deepl.com` (settings.apiUrl (string)).
If I now want to translate a content element with Deepl, I get the error message:

Client error: `POST https://api-free.deepl.com` resulted in a `403 Forbidden` response:
403 Forbidden

I have already renewed the authentication key without success.

There is no real harm and it just contains some backup files but this is a bad practice smell - can be avoided by using .gitattributes, see

https://git-scm.com/book/en/v2/Customizing-Git-Git-Attributes

and then using the "git archive" method for creating the archive.

Or better still, integrate the current way to automatically upload extension to TER.

Is it possible to translate Mask elements?

On every composer command with installed extension there comes this error:

The TYPO3 extension package "web-vision/wv_deepltranslate", does not define an extension key in its composer.json. Please report this to the author of this package. Specifying the extension key will be mandatory in future versions of TYPO3 (see: https://docs.typo3.org/m/typo3/reference-coreapi/master/en-us/ExtensionArchitecture/ComposerJson/Index.html#extra)

This is the mentioned report. 😉

The 'label' in the 'ctrl' section for the table 'tx_deepl_settings' is configured with Deepl settings, which is not a field name in this table.
In the documentation the 'label' property is mentioned as a required string which must be a field name: https://docs.typo3.org/m/typo3/reference-tca/main/en-us/Ctrl/Properties/Label.html#label

If the label was configured as a random text the dbint module crashes with the following error:

Oops, an error occurred!
An exception occurred while executing 'SELECT `uid`, `pid`, `Deepl settings` FROM `tx_deepl_settings` WHERE `pid` NOT IN (...)

Please set label to uid, which is a field in the table. This doesn't impact the usability, because the table is hidden in the backend at all.

Thanks :-)

see PIT-Solutions-Private-Limited/deepltranslate#13

Also, here: thanks for providing the extension. Awesome work!

Glossary: Often longer terms have to be translated, which are then no longer displayed completely in the BE:

Example: Studien-und Prüfungsordnung für das Lehramt der Musik an Grund-, Mittel-und Realschulen sowie Gymnasien der Hochschule für Musik XXXXX (LASPO)

Hello,
is there a plan to make it compatible with latest TYPO3 11.5 version?
Thanks!
Martin

The DeepL glossary is also supported within the API since August 24, 2021.

The glossary functions allow you to create, inspect and delete glossaries. It is available at https://api.deepl.com/v2/glossaries. Glossaries created with the glossary function can be used in translate requests by specifying the glossary_id parameter.

This may improve the output because a more domain specific set of terms is used. For example, for the university we use a term library for English / German which is regularly updated.

• glossary documentation: https://www.deepl.com/docs-api/managing-glossaries/
• Announcing Glossary Support for the DeepL API
• First blog entry for glossary support: https://www.deepl.com/en/blog/20200506

From my point of view there are 2 applications for a glossary or rather a translation matrix.

1. Glossary for human readers
2. Glossary for DeepL automatic translation

What we currently have (https://uol.de/glossar) was originally intended for "humans".

We do of course want to reuse this or parts of it for DeepL, but what is not supported currently (neither by DeepL or the extension) are several target terms.

For example:
DE (source):Abschlussarbeit (Studium)
EN (target):

• thesis
• final project
• final paper

We sometimes have several possible terms where it would be ideal if DeepL could pick the most appropriate one. This is not possible (as it is not supported by DeepL AFAIK). So we will probably create an glossary for automatic translation where we either remove those entries or stick to one target term.

In the long run, it seems to me it would be a good solution if the glossary entries in wv_deepltranslate were flexible - especially if this is also to be displayed in the FE. For the FE (for human readers), we might want to keep those entries (and not have to maintain a second almost identical list elsewhere).

For example, you could have checkboxes, such as

• use for automatic translation
• show in FE

(both selected by default).

This will probably make everything a little more complicated than was originally intended - but here it is important that maybe not everything is implemented but is considered in the concept and can be easily extended.

Reproduce

1. Add language "Turkish"
2. Create page with content and translation page to "Turkish"
3. Click Translate, choose Translate (deepl)
4. an error message appears:

Client error: POST https://api.deepl.com/v2/translate` resulted in a 400 Bad Request response: {"message":"Value for 'target_lang' not supported."}`

I would expect the DeepL translate button to not be displayed if the target language is not supported by DeepL.

i installed the extension and tried to open a page with list. The error message shown is this:

Core: Exception handler (WEB): Uncaught TYPO3 Exception: syntax error, unexpected 'fn' (T_STRING), expecting :: (T_PAAMAYIM_NEKUDOTAYIM) | ParseError thrown in file /usr/www/users/devnax/dev.mysite.com/typo3/releases/95/web/typo3conf/ext/wv_deepltranslate/Classes/Override/DatabaseRecordList.php in line 42. Requested URL: https://dev.mysite.com/typo3/index.php?route=%%2Fweb%%2Flist%%2F&token=--AnonymizedToken--&id=474&

Can't tell why this is happening and how to fix it, hope someone can help me.

If user is logged in in frontend, following javascript is loaded and breaks jquery from default page javascript:

`

How can I disable loading js in frontend?

Hi,

having a already translated container and create a new CE in the default-language container

now try to translate ends in an 400 server error (and a frozen modal) during localization wizard (because the CE inside the container "is not found":

this is due the Xclass of EXT:container is overriden in EXT:wv_deepltranslate
correct behaviour (like in the xclass of the EXT:container)

i will provide a pr

s. also:
#44
b13/container#188

Tested with TYPO3 10.4.26, EXT:container 1.5, EXT:wv_deepltranslate 2.0.1

Maybe the list of supported languages in the Deepl Service ist not up2date. Check: https://www.deepl.com/de/docs-api/translating-text/#request

We installed the latest TER version of this extension into a 10.4.21 TYPO3 installation and tried to translate a standard text content element. We inserted a valid Deepl API Key (according to client) into the extension configuration. When translating in the page module in the last step we get an error message:
Client error: POST https://api.deepl.com/v2/translate resulted in a 403 Forbidden response: {"message":"Wrong endpoint. Use https://api-free.deepl.com"}
Does this clearly say the API key is invalid? Or was there maybe a change in the Deepl API infrastructure?

Our web-site is not httpauth protected at the moment as we thought this could habe been the reason for this error, but it was not. When changing the API endpoint to https://api-free.deepl.com/v2/translate it works.

deepl 2.2.1

please 'Beschreibung' not ' Beschriebung'.

deepl 2.2.1
TYPO3 10.4.31

All glossary entries are in a folder. When searching for a term with the magnifying glass in the header, I never get hits.

We are testing the glossary functionality in our project (Uni-Osnabrück). Works good, but I found no easy way - as an editor - of deleting a glossary entry.

We allow editors to create tx_wvdeepltranslate_domain_model_glossaries which works great when creating new glossary items. This auto-generates DB entries tx_wvdeepltranslate_domain_model_glossariessync which are just a json representation of the "translation item" (for the API, I suppose) and are not really manageble manually, since they have an UUID as a title.

I want, as an editor, to be able to delete a glossary term and its translation, by simply removing the tx_wvdeepltranslate_domain_model_glossaries entries - and have the API resolve which tx_wvdeepltranslate_domain_model_glossariessync entries to delete (or update) on their own.

Any chance of doing having that missing feature included in a future release?

Kind regards,
Ernesto

API key and URL are set, languages are configured in the extension settings. When translating a page with the 'Translate (deepl)' option, it's loading forever and no signs of my DeepL budget are used. The option 'Translate (Google)' is just reproducing the original text without translation. The other options are not working either for me. How can this be fixed?

Thank you for this great Extension.
My client asked me if i can set the option "formality" to "more". API-Doc

Unfortunately there are no settings for this, can you add this to the next version?

• "ID" - Indonesian
• "TR" - Turkish

For example, since the last version 2.0.1, code like the following is used:

$possibleTranslations = array_map(static fn($siteLanguage) => $siteLanguage->getLanguageId(), $this->languagesAllowedForUser);

https://github.com/web-vision/wv_deepltranslate/blob/2.0.1/Classes/Override/DatabaseRecordList.php#L42

This is only compatible with PHP 7.4 and up.

Compatibility with PHP <=7.3 is no longer given. Please make the version compatible to PHP < 7.4 or adjust the requirements accordingly.

When a content element has a start date in the future, the translation process is not completed (It's the same behaviour like #79)

Hi,

Thank you so much for this awesome extension with the cool translating options.

Is this possible to make translation for the DCE (dynamic content element) elements?

Please share your thought on it asap.

Thanks again
Team Vbuilt Solution

Servus,

nach der Installation in 10.4.5 und Konfiguration laut Anleitung einschließlich neuem API-Key von Deepl hängt die Übersetzung im 3. Schritt, egal was man auswählt.
Woran kann es liegen?

Hello,

after updating from version 2.0.0 to version 2.0.1 using Composer, I get the following error message:

Too few arguments to function WebVision\WvDeepltranslate\Override\DatabaseRecordList::makeLocalizationPanel(), 2 passed in XXX/typo3/sysext/recordlist/Classes/RecordList/DatabaseRecordList.php on line 1342 and exactly 3 expected

Running Analyze Database Structure did nothing.

Best wishes
EPOCHE NAPOLEON

On TYPO3 10.4.23 with wv_deepltranslate 2.0.1 on PHP 7.4 the following error occurs in the list module on any page:

Oops, an error occurred!
Too few arguments to function WebVision\WvDeepltranslate\Override\DatabaseRecordList::makeLocalizationPanel(), 2 passed in /typo3/sysext/recordlist/Classes/RecordList/DatabaseRecordList.php on line 1342 and exactly 3 expected

Hi.
I've downloaded your extension for Typo3 and when I try to translate a small media&test containing Hello World in the processing step it stops. When I refresh the page in my logs I see an error:
Core: Exception handler (WEB): Uncaught TYPO3 Exception: cURL error 56: Recv failure: Connection reset by peer (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) | GuzzleHttp\Exception\RequestException thrown in file /home/user/Projects/test/vendor/guzzlehttp/guzzle/src/Handler/CurlFactory.php in line 201.

The test environment is on a local machine with apache2. Curl enabled.

Best Regards.

Are you planning on providing an update of your extension to be available soon for TYPO3 11 LTS?

Hello Community,

i installed the wv_deepltranslate extension on a Typo3 Version 10 Project.

I've already set the Deepl APi Key and the other configs.

But when i tried to translate a standard CE like Text with Picture it doesn't show the translation.

My Deepl character consumption is counting every translation.

Does somebody has any idea?

TYPO3 v10.4.27 with EXT:wv_deepltranslate v2.0.1
require.js and requirejs-loader.js x and y are loaded in the frontend and cause errors there.

Ampersands in headlines or texts (plain texts, no RTE) are not decoded and are stored as "&amp;" in database.

To reproduce:

1. Create an CE with an ampersand character in headline.
2. Translate CE via deepl extension
3. View CE in frontend or in database

Obviously only ampersand character is affacted.

Using branch: glossary-integration with TYPO3 v11

Exception:

Call to a member function getLanguageIsoCode() on null

in /var/www/t3dev.uni-oldenburg.de/htdocs/typo3conf/ext/wv_deepltranslate/Classes/Hooks/DataHandlerHook.php line 63
        $this->languageRepository = $objectManager->get(LanguageRepository::class);

        $systemLanguages = $this->languageRepository->findAll();
        $defaultLanguage = $this->languageRepository->findByUid(0);
        $defaultLangIso = $defaultLanguage->getLanguageIsoCode();

        if ($systemLanguages->count() > 0) {

In my current test installation (which is based on the TYPO3 base distribution with introduction package, there is no sys_language record 0. There is no language record for the default language. I am not sure if it is necessary for the default language.

select uid,title from sys_language ;
+-----+--------+
| uid | title  |
+-----+--------+
|   1 | Dansk  |
|   2 | German |
+-----+--------+

(You can setup a basic base distribution, see https://docs.typo3.org/m/typo3/tutorial-getting-started/main/en-us/Installation/Install.html#install)

composer create-project typo3/cms-base-distribution:^11 t3intro11
composer require typo3/cms-introduction:^4.4.1

So, not sure how to best handle this, but relying on the record with uid=0 exists in sys_language - may not always work.

Hello!

I use wv_deepltranslate V.1.1.2 under Typo3 V.9.5. I get the following error when translating in list mode (e.g. for a news article) into a language not supported by Deepl (e.g. Czech, Russian or Turkish)

{"status":"false","message":"Client error: POST https:\/\/api.deepl.com\/v2\/translate resulted in a 400 Bad Request response:\n{"message":"Value for 'target_lang' not supported."}\n"}

Thanks for your response in advance!

At the moment, the translation buttons are always displayed and when you click on them, you get a message that the settings have to be completed.

Of course, an editor can't do much with that at first. My suggestion: Only show the buttons if the API settings exist.

The elements are created but the content gets not translated by deepl.

Is there a chance to get support for b13/container?
Maybe this can be solved already with some configuration?

See https://www.deepl.com/de/docs-api/translating-text/#request

"EN-GB" - English (British)
"EN-US" - English (American)
"EN" - English (unspecified variant for backward compatibility; please select EN-GB or EN-US instead)

Hi,

I found this extension and tried to use it the first time. I use TYPO3 11.5.12 with PHP 8.0 on ddev. After installing the extension by composer I added the API key from deepl (from Google I don't want to use). I included Typoscript, languages (DE/EN) are configured and working. The TCA stuff I skipped to test the extension first basically. When I want to translate a page ("create a new translation of this page") I'm getting the following error message only:

Line 82 means $customMode = $cmdmap['localization']['custom']['mode'];

I can't find anything neither in the docs nor in Typoscript to set something like a "mode". Maybe it's a bug.

Best,
Markus

If I used this with typo3 in version 10.4.13 i became an error:

Core: Exception handler (WEB): Uncaught TYPO3 Exception: Too few arguments to function TYPO3\CMS\Backend\Controller\Page\LocalizationController::getPageColumns(), 1 passed in /var/www/html/public/typo3conf/ext/wv_deepltranslate/Classes/Override/LocalizationController.php on line 188 and exactly 3 expected

This is the line:

return (new JsonResponse())->setPayload([
   'records' => $records,
   'columns' => $this->getPageColumns($pageId),
   ]);

If i edited it to this:

return (new JsonResponse())->setPayload([
   'records' => $records,
   'columns' => $this->getPageColumns($pageId, $records, []),
   ]);

it will work.
But it is not a good practice to work in the extension files.