Unable to Rollout Jcr:title, jcr:description..etc | Community
Skip to main content
S
SekharBu1
Level 2
January 7, 2025
Solved

Unable to Rollout Jcr:title, jcr:description..etc

  • January 7, 2025
  • 2 replies
  • 702 views

We have a Rollout configuration "updateContentActionFactory". In side that, there is a property "jcr:.*". I am able to rollout jcr:title, jcr:description, ... for the first time rollout once I create a page. I am unable to rollout the same properties by updating from next rollout onwards. We want to rollout the jcr:title, jcr:description.. etc properties to some pages even there is "updateContentActionFactory" configuration. 

please suggest me if there is any possibility to do so. 

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 SreenivasBr

If you want all jcr: properties to be rolled out, then you should remove jcr:.* from the OSGi config. But I am not sure if it is right thing to do. You might have to check the impact.

2 replies

SreenivasBr
SreenivasBr
Level 4
January 8, 2025

You can change the expressions defining the exclusion list as required.

For example, if you want the page Title to be included in the changes considered for rollout, remove jcr:title from the exclusions. For example, with the regex:

jcr:(?!(title)$).*

 

Refer - https://experienceleague.adobe.com/en/docs/experience-manager-65/content/sites/administering/introduction/msm-sync#cq-msm-content-update-action-exclusions

    S
    SekharBu1Author
    Level 2
    January 21, 2025

    Previously e were able to rollout jcr:title and jcr:description properties even there is jcr:.* in Excluded Page Properties for some pages. But now we are unable to rollout the properties for any page in the site. is there any other way to rollout jcr: properties even there is jcr:.* with out using jcr:(?!(title)$).* ..etc

    SreenivasBr
    SreenivasBrAccepted solution
    Level 4
    January 22, 2025

    If you want all jcr: properties to be rolled out, then you should remove jcr:.* from the OSGi config. But I am not sure if it is right thing to do. You might have to check the impact.

      kautuk_sahni
      Community Manager
      kautuk_sahniCommunity Manager
      Community Manager
      February 10, 2025

      @sekharbu1 Did you find the suggestion helpful? Please let us know if you need more information. If a response worked, kindly mark it as correct for posterity; alternatively, if you found a solution yourself, we’d appreciate it if you could share it with the community. Thank you!

      Kautuk Sahni
      Terms & ConditionsAccessibility statement

      Loading footer...