Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Creating translation of page using the "Page" module fails with error message #206

Closed
Stuffy opened this issue May 9, 2023 · 2 comments · Fixed by #211
Closed
Labels
bug Something isn't working

Comments

@Stuffy
Copy link

Stuffy commented May 9, 2023

When trying to translate a page using the "Page" module, an error occurs during step 1 of the translation process. The error message is Please complete missing deepl configurations. .

To Reproduce
Create "Sites"-Configuration, and create a few content elements on a page with content that you want to have translated.
Using the "Page"-Module, try to translate said content elements using the translation-wizard. This will fail with the error message mentioned above.

Expected behavior
The translation wizard should progress to the next step and allow translation of the content.

Screenshots
wv_deepltranslate_issue

TYPO3 Setup

  • TYPO3 Version: 11.5.27
  • Server: Apache
  • Database type and version: MySQL 8.0.25
  • PHP version: 7.4.33
  • DeepL free or paid API?: Both result in the same error
  • composer or classic setup? composer
@Stuffy Stuffy added the bug Something isn't working label May 9, 2023
Stuffy pushed a commit to Stuffy/wv_deepltranslate that referenced this issue May 9, 2023
@georgschurkin
Copy link

I have the same problem with TYPO3 9. By the way, the translation in the "List" module works pretty well.

@bigahuna
Copy link
Contributor

Same problem here. It seams that the extension setting (apiKey) is not available inside "Page" module translations

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants