[EXCONTRANS-317] Google translator config doesn't get registered Created: 22/Aug/19  Updated: 11/Nov/19  Resolved: 11/Nov/19

Status: Closed
Project: Content Translation Extended (CTX)
Component/s: Google Translator
Affects Version/s: 3.0
Fix Version/s: None

Type: Bug Priority: High
Reporter: Edwin Guilbert Assignee: Trung Luu
Resolution: Workaround exists Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Magnolia 6.1


Attachments: PNG File Screenshot 2019-08-22 at 16.29.11.png     PNG File Screenshot 2019-08-22 at 16.31.52.png    
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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled

 Description   

Adding a properly configured config node to content-translation-support-ext-google module doesn't seem to register a possible translator when trying to add a page to a translation batch.

Modules im using:

    <dependency>
        <groupId>info.magnolia.translation</groupId>
        <artifactId>magnolia-content-translation-support-ext-core</artifactId>
        <version>3.0-SNAPSHOT</version>
    </dependency>
    
    
    <dependency>
        <groupId>info.magnolia.translation</groupId>
        <artifactId>magnolia-content-translation-support-ext-google</artifactId>
        <version>3.0-SNAPSHOT</version>
    </dependency>

Config used: Screenshot 2019-08-22 at 16.29.11.png

Dialog where the translator is not being shown: Screenshot 2019-08-22 at 16.31.52

 



 Comments   
Comment by Edwin Guilbert [ 11/Nov/19 ]

defaultFlag and enabledFlag properties were missing. It worked fine after adding them

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