mpmuradov
Community profile mpmuradov Level 1
Job title here
Location here
0 BADGES
Level 1

Level 1

Learn more
Joined the community 30-10-2020 5:48:50 AM
Offline
Top badges earned by mpmuradov
Customize the badges you want to showcase on your profile
Re: AEM Cloud. What package may contain indices
Avatar
Level 1
mpmuradov
Level 1

Likes

0 likes

Total Posts

6 posts

Correct reply

0 solutions
View profile
mpmuradov
- Adobe Experience Manager
/apps and /oak:index are in the same package on the picturehttps://experienceleague.adobe.com/docs/experience-manager-cloud-service/assets/content-package-organization.png?lang=en

Views

83

Likes

0

Replies

0
Re: AEM Cloud. What package may contain indices
Avatar
Level 1
mpmuradov
Level 1

Likes

0 likes

Total Posts

6 posts

Correct reply

0 solutions
View profile
mpmuradov
- Adobe Experience Manager
I mentioned the same link ))Both /apps and /oak:index should be put into ui.apps package according to the doc. Here is explanationFor this reason, although Oak indexes are mutable at run time, they must be deployed as code so that they can be installed before any mutable packages are installed. Therefore /oak:index configurations are part of the Code Package and not part of the Content Package

Views

87

Likes

0

Replies

0
AEM Cloud. What package may contain indices
Avatar
Level 1
mpmuradov
Level 1

Likes

0 likes

Total Posts

6 posts

Correct reply

0 solutions
View profile
mpmuradov
- Adobe Experience Manager
Hi there! I build a translation connector with ui.apps package and put `/apps/smartling-connector` and `/oak:index` into them.Embedded the connector into WKND site project and deployed them into AEM Cloud. AEM Cloud Code Scanning says this warning:Inclusion of both /apps/smartling-connector and /oak:index/smtl.fileUri-custom-1 in the same package violates the separation of immutable and mutable paths in the same package.But according to https://experienceleague.adobe.com/docs/experience-manager-...

Views

119

Likes

0

Replies

3
Re: Wrong links to XF on translated page
Avatar
Level 1
mpmuradov
Level 1

Likes

0 likes

Total Posts

6 posts

Correct reply

0 solutions
View profile
mpmuradov
- Adobe Experience Manager
Hi @rush_pawan. FR page should refer to FR XF, but it refer to LAUNCH of FR XF. Moreover, this launch is removed after translation, because AEM creates translation project with enabled `Delete launch after translation` option by default. What should be updated for translation rollout config to fix the issue?

Views

99

Likes

0

Replies

0
Wrong links to XF on translated page
Avatar
Level 1
mpmuradov
Level 1

Likes

0 likes

Total Posts

6 posts

Correct reply

0 solutions
View profile
mpmuradov
- Adobe Experience Manager
Hi, Found out an issue with translated page contained a link to XF. If source page referred to a XF, translated page refers to a launch of XF.For example, source page /content/we-retail/language-masters/en/page has a XF component with link to /content/experience-fragments/we.retail/en/test-XF. The page is sent for translation to `fr` and there are two launches: for page and XF. /content/LAUNCH/content/we-retail/language-masters/fr/page refers to /content/LAUNCH/content/experience-fragments/we.re...

Views

128

Likes

0

Replies

2
AEM resets back translations of XFs
Avatar
Level 1
mpmuradov
Level 1

Likes

0 likes

Total Posts

6 posts

Correct reply

0 solutions
View profile
mpmuradov
- Adobe Experience Manager
Hello! I'm encountered an issue with translation of XF within a page. AEM resets back translated `fr` XFs to original `en` language.Let me explain with reproduce steps. We can do it with We.Retail example:1. Create XF1 /content/experience-fragments/we.retail/en/XF1 and put text component on it. Type some text2. Create XF2 /content/experience-fragments/we.retail/en/XF2and put text component on it. Type some text3. Translate both XFs to `fr` locale: /content/experience-fragments/we.retail/fr/XF1 a...

Views

92

Likes

0

Replies

0