Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

Where is the i18n translator UI for AEM Cloud?

Avatar

Avatar
Boost 25
Level 4
TB3dock
Level 4

Likes

28 likes

Total Posts

181 posts

Correct Reply

4 solutions
Top badges earned
Boost 25
Give Back 25
Validate 10
Validate 1
Ignite 5
View profile

Avatar
Boost 25
Level 4
TB3dock
Level 4

Likes

28 likes

Total Posts

181 posts

Correct Reply

4 solutions
Top badges earned
Boost 25
Give Back 25
Validate 10
Validate 1
Ignite 5
View profile
TB3dock
Level 4

18-03-2021

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.

 

 

View Entire Topic

Avatar

Avatar
Affirm 100
Level 10
asutosh_jena
Level 10

Likes

404 likes

Total Posts

502 posts

Correct Reply

137 solutions
Top badges earned
Affirm 100
Ignite 1
Establish
Give Back 50
Give Back 5
View profile

Avatar
Affirm 100
Level 10
asutosh_jena
Level 10

Likes

404 likes

Total Posts

502 posts

Correct Reply

137 solutions
Top badges earned
Affirm 100
Ignite 1
Establish
Give Back 50
Give Back 5
View profile
asutosh_jena
Level 10

18-03-2021

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!