Expand my Community achievements bar.

Guidelines for the Responsible Use of Generative AI in the Experience Cloud Community.
SOLVED

Restricting a specific node of a page from getting activated

Avatar

Level 1

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.

1 Accepted Solution

Avatar

Correct answer by
Level 10

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

View solution in original post

1 Reply

Avatar

Correct answer by
Level 10

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