AEM-6.5 Page properties not being reverted when i click on revert to this version | Community
Skip to main content
N
narayanad670284
Level 2
December 23, 2020
Solved

AEM-6.5 Page properties not being reverted when i click on revert to this version

  • December 23, 2020
  • 2 replies
  • 1452 views

Hello

We have some custom page properties included in the page props section. Also we are creating a version when we rollout. The issue is after i rollout to the target and select the target page and go to the timeline column and click on revert to this version, the page properties that we have added are not being reverted. The properties that are not being reverted does not start with jcr:, sling: or cq:

Thanks in advance!

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 Ravi_Pampana

Hi,

 

Is your page properties are starting with cq:, jcr: or sling:, if so then those properties will be ignored in rollout. 

 

Refer https://helpx.adobe.com/se/experience-manager/kb/MSMRolloutConfig.html for more details. 

 

Hope this helps!

2 replies

Ravi_Pampana
Community Advisor
Ravi_PampanaCommunity AdvisorAccepted solution
Community Advisor
December 23, 2020

Hi,

 

Is your page properties are starting with cq:, jcr: or sling:, if so then those properties will be ignored in rollout. 

 

Refer https://helpx.adobe.com/se/experience-manager/kb/MSMRolloutConfig.html for more details. 

 

Hope this helps!

    N
    narayanad670284Author
    Level 2
    December 23, 2020
    hey.. the properties are not started with jcr or cq or sling.
    shelly-goel
    Adobe Employee
    shelly-goelAdobe Employee
    Adobe Employee
    December 25, 2020

    @narayanad670284 

    If any of the properties like navTitle, pageTitle, or subtitle (not starting with cq, jcr, or sling) are modified on a we.retail example site, and following same steps as yours, the properties do revert back to what was set in the previous version.

    It must be something to do with your custom implementation or how the versions are created.

      Terms & ConditionsAccessibility statement

      Loading footer...