JCR property jcr:mixinTypes with granite:AuthenticationRequired is not rolling out | Community
Skip to main content
bpeddapudi
Level 2
November 16, 2022
Solved

JCR property jcr:mixinTypes with granite:AuthenticationRequired is not rolling out

  • November 16, 2022
  • 1 reply
  • 973 views

Need advice on this guys,


I have a Blueprint Page (/content/mysite/master/en/testpage) and Live Copy (/content/mysite/us/en/testpage).
I gated the Blueprint page by enabling "Authentication Requirement". Behind the scene it's adding  jcr:mixinTypes property with value granite:AuthenticationRequired. When this page is rolledout the Live Copy is not receiving this jcr property.
Regular content changes are reflecting though.

 

I tried updating "WCM Rollout Manager" config with "jcr:(?!(mixinTypes)$).*" but still "jcr:mixinTypes" property is still not rolling out to Live copy.

+Rollout Manager config:

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 BrijeshYadav

As par the "ContentUpdateActionFactory"Java class 

 

This is a special case for which you need to add "jcr:(?!(mixinTypes)$).*" to "Ignored Mixin NodeTypes"


I would recommend to be extra careful while playing with mixiTypes

1 reply

BrijeshYadav
Level 5
November 16, 2022

Hi @bpeddapudi ,
You need to use "CQ MSM Content Update Action" configuration instead of "WCM Rollout Manager" because before 5.5 SP2, the excluded page properties were configured in the system console under the "Day CQ WCM Rollout Manager." With 5.5 SP2 and later, the excluded page properties settings within that panel are ignored. Property exclusion on rollout is configured in "CQ MSM Content Update Action."

/Brijesh Yadav

bpeddapudi
Level 2
November 16, 2022

Hi @brijeshyadav I updated "CQ MSM Content Update Action" configuration too but still "jcr:mixinTypes" is not copied to Live copy.

BrijeshYadav
BrijeshYadavAccepted solution
Level 5
November 17, 2022

As par the "ContentUpdateActionFactory"Java class 

 

This is a special case for which you need to add "jcr:(?!(mixinTypes)$).*" to "Ignored Mixin NodeTypes"


I would recommend to be extra careful while playing with mixiTypes