[EXCONTRANS-374] Provide default sample config in translation modules Created: 04/May/22  Updated: 04/Oct/22  Resolved: 04/Oct/22

Status: Closed
Project: Content Translation Extended (CTX)
Component/s: None
Affects Version/s: 3.4.5
Fix Version/s: 3.4.6

Type: Improvement Priority: Neutral
Reporter: Richard Gange Assignee: Teresa Miyar
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:

 Description   

It would be helpful for users if each of the translation modules provided a default sample configuration. This would allow users to decorate from their light module rather and having to create nodes and properties in JCR.

For example:

'config':
  'jcr:primaryType': 'mgnl:content'
  'Deepl':
    'autoTranslationAllowed': 'false'
    'class': 'info.magnolia.translation.ext.provider.deepl.definition.DeeplProviderDefinition'
    'clientId': 'not_in_use'
    'clientToken': '279a2e9d-83b3-c416-7e2d-f721593e42a0:fx'
    'configName': 'DeepL.com'
    'enabledFlag': 'true'
    'implementationClass': 'info.magnolia.translation.ext.provider.deepl.translator.DeeplTranslator'


 Comments   
Comment by Pierre Sandrin [ 24/Aug/22 ]

Having a JCR view of the config would make it more clear that you have to add the config in the JCR (and not via decoration). And it would also be great to make a note in the Documentation until this issue is resolved.
https://docs.magnolia-cms.com/content-translation-support-ext/deepl/index.html

Generated at Mon Feb 12 00:30:37 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.