MSM | Rollout 2 languages into one | Community
Skip to main content
Adobe Employee
October 20, 2022
Solved

MSM | Rollout 2 languages into one

  • October 20, 2022
  • 2 replies
  • 827 views

Hello Experts,

 

We have a scenario where customer wants to roll out 2 different language under 1 parent for example, there are 2 language copy "en" and "fr". Both of these language copies is needed to be rolled out to "/content/abc/us/en". Is there any issue doing so? or any solution to achieve this?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by joerghoh

That requirement feels quite strange and in my opinion it points to a problem in your content architecture.

 

In AEM languages are normally organized in sibling folders which helps you to build navigation and ease the permission model.

Also the MSM is not designed to rollout 2 blueprints into a single folder. While it might work on the first rollout, please  check the behavior when it comes to duplicate page names and changes there. I would even go that far and say that this scenario is not supported, because it deviates quite a lot from the documentation.

2 replies

ksh_ingole7
Community Advisor
Community Advisor
October 20, 2022

Hi @anikaag 

 

You can rollout the language copies to "/content/website/us/en" and "/content/website/us/fr". That's a valid scenario. 

 

Thanks

joerghoh
Adobe Employee
joerghohAdobe EmployeeAccepted solution
Adobe Employee
October 21, 2022

That requirement feels quite strange and in my opinion it points to a problem in your content architecture.

 

In AEM languages are normally organized in sibling folders which helps you to build navigation and ease the permission model.

Also the MSM is not designed to rollout 2 blueprints into a single folder. While it might work on the first rollout, please  check the behavior when it comes to duplicate page names and changes there. I would even go that far and say that this scenario is not supported, because it deviates quite a lot from the documentation.