Expand my Community achievements bar.

SOLVED

Where is the i18n translator UI for AEM Cloud?

Avatar

Level 9

Adobe AEM provides a UI where you can edit, export and import your i18n strings for translation:

 

https://experienceleague.adobe.com/docs/experience-manager-65/developing/components/internationaliza...

 

The URL should be /libs/cq/i18n/translator.html

 

When we use this URL on our local cloud SDK install, it works. When we use the same URL on our AEM Cloud instance, we get a generic 403 message back.

 

We have raised a support ticket with Adobe, but they have not been able to provide any answer.

 

Does anyone else have this issue with AEM cloud, i.e. no UI to export, import or translate i18n?

 

We are admin users of the AEM author instance.

 

 

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi @TB3dock 

As per Adobe documentation, in AEM as a Cloud Service, any chnages to the i18n needs to be deployed as part of the code.

"I18n translation changes need to come from Git via the CI/CD pipeline."

 

Even I too have also facing the same issue with Cloud Service and it gives me the same 403 error. This is basically not available for cloud users.

/apps and /libs are immutable at runtime so this has to be deployed by Git.

 

Hope this helps!
Thanks!

View solution in original post

4 Replies

Avatar

Community Advisor

@TB3dock - It seems like it's not allowed in AEM on cloud. You need to check with Adobe Support team.
I think other way would be to send it as part of the code itself.

Thanks,
Nikhil Kumar

Avatar

Level 9
Thanks Nikhil-Kumar, If this is correct, that cloud doesnt have the translator, this is something of a showstopper for using cloud. Its not viable to tie translations (Which are content) to releases, they have to be editable by the content teams.

Avatar

Correct answer by
Community Advisor

Hi @TB3dock 

As per Adobe documentation, in AEM as a Cloud Service, any chnages to the i18n needs to be deployed as part of the code.

"I18n translation changes need to come from Git via the CI/CD pipeline."

 

Even I too have also facing the same issue with Cloud Service and it gives me the same 403 error. This is basically not available for cloud users.

/apps and /libs are immutable at runtime so this has to be deployed by Git.

 

Hope this helps!
Thanks!