Restricting a specific node of a page from getting activated | Community
Skip to main content
Laamor
Laamor
October 16, 2015
Solved

Restricting a specific node of a page from getting activated

  • October 16, 2015
  • 1 reply
  • 528 views

The “activate page” option present in the sidekick of the author instance replicates all the child/subchild nodes of that page on the publish instance.

But, we want to restrict a specific child node from getting published on the publish instance.

Please suggest.

 

For example, in the attached screenshot,  We have a cq:page type node named "rewards". While activating this page from Sidekick, I do not want the node "designpackage" to get published.

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 Sham_HC

Hi Rachna Goel,

What is the exact use case you are trying to implement? You can use create customer user with all access and restricting designpackage. And use that user in Agent User Id of replication.   An reference sample at http://aemfaq.blogspot.com/2013/05/how-to-configure-replication-agent-to.html

To me looks right way to solve is by modfying your designpackage Component to have a condition of checking run mode and display it rather than restricting at replication level.

Thanks,

Sham

1 reply

Sham_HC
Sham_HCAccepted solution
Level 10
October 16, 2015

Hi Rachna Goel,

What is the exact use case you are trying to implement? You can use create customer user with all access and restricting designpackage. And use that user in Agent User Id of replication.   An reference sample at http://aemfaq.blogspot.com/2013/05/how-to-configure-replication-agent-to.html

To me looks right way to solve is by modfying your designpackage Component to have a condition of checking run mode and display it rather than restricting at replication level.

Thanks,

Sham

Terms & ConditionsAccessibility statement

Loading footer...