Title Issue in AEM Multi-Country Site Creation from Blueprint

[julkarna]

Hi everyone,

I'm working on a multi-country AEM project where we create sites using blueprints. In my local environment, the title of the country is set correctly when I create a site (e.g., "United States" with a node name of "us"), and the title reflects my input. However, in our dev environment, the node name is fine, but the country title defaults to "language-masters" instead of my provided title. Has anyone encountered this issue before? Could it be a problem with blueprint configuration or rollout behavior? Any insights would be appreciated!

[Ritesh_Mittal]

Hi @julkarna ,

Were you able to resolve this issue? If not, here are a few things you can check -

• Ensure the blueprint is correctly configured with the title property in both environments. It’s possible the title is not properly set in the blueprint in the dev environment.
• Check the rollout logs to verify if the title is being correctly propagated during the rollout process. If there are any issues, the title may not be set correctly.
• If you're working with multi-country sites, make sure the title property is properly translated and set in the dev environment. Missing translations could cause the fallback to "language-masters".
• Compare your local and dev environment configurations, focusing on any differences related to blueprints, workflows, or content models.

Let me know if you're still facing this issue or above steps helped.

Thanks,

Ritesh Mittal

[kautuk_sahni]

@EstebanBustamante @Tethich @SureshDhulipudi @martin_ecx_io @Saravanan_Dharmaraj @BrianKasingli @pradeepdubey82 @abhishekanand_ @Anil_Chennapragada @daniel-strmecki would you please take a moment to review this question? We would be grateful if you could share your suggestion on this question.

[EstebanBustamante]

Hi,

I have never encountered this issue before, and since it is not reproducible on your local setup, it must be related to your Dev environment. I would suggest pulling the configurations from the Dev environment into your local to ensure they are not the cause of the problem.

Hope this helps.