Expand my Community achievements bar.

SOLVED

Adjust translation config on AEMaaCS

Avatar

Level 2

We want to adjust the translation config which is stored in /libs/settings/cloudconfigs. When an author starts the "Language copy" workflow for a page, the adjusted translation config should be active. For example: We want to deactivate the "Assets Translation". 

1 Accepted Solution

Avatar

Correct answer by
Level 2

Solved it. 

How?

Create an own translation config with a different name than "default_configuration".

Default wise, there is a /libs/translationcfg/default_configuration which you cannot change. But there is also a /conf/global/translationcfg/default_configuration - here we can adapt the configuration. But it doesn't matter what we define; it has no impact. Something we need to check with Adobe, if this is per design. 

 

So we have created a new translation config in /conf/ with a different name than "default_configuration". Now our configuration works. 

View solution in original post

3 Replies

Avatar

Community Advisor

@Steu86 have you tried overlaying the node in /libs/ path to /apps/ path then changing the required properties in /apps/ path?

Avatar

Level 2

@Shashi_Mulugu not able to create a translation configuration in /apps/ within author (I'm admin). There is no create button. I'm trying to follow this doc https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/sites/administering...

In the meantime, we have tried to create an own translation configuration in /conf/. We have also been able to select this configuration manually in the Language copy workflow. But when processing this workflow, we still don't see any changes. The entire translation still follows the default_configuration in /libs/translationcfg/default_translation.

Avatar

Correct answer by
Level 2

Solved it. 

How?

Create an own translation config with a different name than "default_configuration".

Default wise, there is a /libs/translationcfg/default_configuration which you cannot change. But there is also a /conf/global/translationcfg/default_configuration - here we can adapt the configuration. But it doesn't matter what we define; it has no impact. Something we need to check with Adobe, if this is per design. 

 

So we have created a new translation config in /conf/ with a different name than "default_configuration". Now our configuration works.