Filter Nodes while publishing | Community
Skip to main content
Krishna_C
Level 3
October 16, 2015
Solved

Filter Nodes while publishing

  • October 16, 2015
  • 4 replies
  • 1349 views

Hi Everyone,

I have a use case where I have restrict some nodes below the  jcr:content/node1/node2(to be restricted)  when I publish the page.

I tried it using ACL,   restricting the read access on the node to be restricted and the publish the page. I cant see the node in CRX since I don't have permission to read but still when I publish the page everything is getting published.

Can some one tell me a way where I can restrict the node from getting published.

Thanks & Regards,

Krishna

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 joerghoh

Hi,

at the moment it isn't possible to filter nodes either on the creation of the payload or on unwrapping it on the target system. I would recommend to file an enhancement request in Daycare, if you really need it. At the moment you could use wildcard ACLs on publish to restrict access, if you can model your ruleset accordingly.

kind regards,
Jörg

4 replies

joerghoh
Adobe Employee
joerghohAdobe EmployeeAccepted solution
Adobe Employee
October 16, 2015

Hi,

at the moment it isn't possible to filter nodes either on the creation of the payload or on unwrapping it on the target system. I would recommend to file an enhancement request in Daycare, if you really need it. At the moment you could use wildcard ACLs on publish to restrict access, if you can model your ruleset accordingly.

kind regards,
Jörg

Sham_HC
Level 10
October 16, 2015

Hi Krishna,

  Writing custom replication agent OR packaging acl then activating are alternatives.
 
Thanks,
Sham
Twitter: @adobe_sham

Krishna_C
Krishna_CAuthor
Level 3
October 16, 2015

Hi Sham,

Thanks for the reply.

Now I have my requirement changes. So no worries now :)

Regards,

Krishna

Krishna_C
Krishna_CAuthor
Level 3
October 16, 2015

Thanks for the reply Jörg .

Solution of restricting access in publish is a good alternative. Not sure we can use it that way.

Regards,

Krishna