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

SOLVED

MSM : sling:vanityPath dosent get created

manal-ghanim
Level 2
Level 2

Hi,

When creating a live copy in AEM 6.5, the property sling:vanityPath doesn't get copied.

The OSGI configurations "Day CQ WCM Rollout Manager" and "CQ MSM Content Copy Action" are supposed to filter all the sling:* props, but still, only vanity seems to be excluded.

Is there a special configuration that explains this behavior ? how can we get vanity to get copied for the live copy ?

Thanks,

1 Accepted Solution
Dipti_Chauhan
Correct answer by
Community Advisor
Community Advisor

Hi @manal-ghanim 

 Can you please share Regex you added in osgi to ignore vanity?

 

and to exclude some properties you need to update these two configuration

  1. CQ MSM content update action
  2. Day CQ WCM Rollout Manage

 

As you said by default all Sling.* properties are excluded but if you want sling:vanityPath to be part of rollout you can update exclude properties in config.

sharing example :

sling:(?!(resourceType|vanityPath|alias)$).*

This is how you can update exclude configuration for multiple properties.

 

Hope this helps!!

thanks

dipti

View solution in original post

2 Replies
Dipti_Chauhan
Correct answer by
Community Advisor
Community Advisor

Hi @manal-ghanim 

 Can you please share Regex you added in osgi to ignore vanity?

 

and to exclude some properties you need to update these two configuration

  1. CQ MSM content update action
  2. Day CQ WCM Rollout Manage

 

As you said by default all Sling.* properties are excluded but if you want sling:vanityPath to be part of rollout you can update exclude properties in config.

sharing example :

sling:(?!(resourceType|vanityPath|alias)$).*

This is how you can update exclude configuration for multiple properties.

 

Hope this helps!!

thanks

dipti

View solution in original post

Arun_Patidar
Community Advisor
Community Advisor

Hi,

As you already mentioned from where you need to enable to rollout sling:vanityPath property that will resolve your problem but I would suggest considering below point before you enable.

sling:vanityPath allows to create alternative url/path to access the page, if you rollout the page and sling:vanityPath property also rollout then there will be 2 AEM pages with the same vanity path which is wrong, however, if you have to roll out the page for another portal/site, then you are safe from end-user point of view but you might have issues in Author and Dispatcher(cache/filter managment)