Multifield Rollout in AEM 6.5.20.0 on-prem | Community
Skip to main content
S
Shaheena_Sheikh
Level 6
November 19, 2024
Solved

Multifield Rollout in AEM 6.5.20.0 on-prem

  • November 19, 2024
  • 1 reply
  • 612 views

Hi All,

I have we-retail content.

I used the teaser component and rolled out. In the Live copy page, I saw the properties jcr:mixinTypes = cq:LiveRelationship on all teaser and its child nodes. On breaking inheritance, I saw teaser node had jcr:mixinTypes = cq:LiveRelationship, cq:LiveSyncCancelled and another property cq:isCancelledForChildren = true. The child nodes still had jcr:mixinTypes = cq:LiveRelationship.

 

I authored teaser in the live copy page, all the child node property jcr:mixinTypes = cq:LiveRelationship were gone. The teaser node was still having the properties intact. I enabled the inheritance again and synced the component. I checked the nodes again, the teaser node only had jcr:mixinTypes = cq:LiveRelationship, and the child nodes didn't have any jcr:mixinTypes. The child nodes also had the authored content that I added in the live copy.

The rollout was also not working. The async rollout job was also failing. The notification shows "Job failed due to an exception (Activation did not set happen)."

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 arunpatidar

Hi @shaheena_sheikh 

You can refer below document to check the impact of handle conflicts

https://experienceleague.adobe.com/en/docs/experience-manager-65/content/sites/administering/introduction/msm-rollout-conflicts 

1 reply

arunpatidar
Community Advisor
arunpatidarCommunity Advisor
Community Advisor
November 19, 2024

Hi @shaheena_sheikh 
Can you please check the teaser component's cq:isContainer property?

 

 

In a rollout the component itself and all its children are replaced with those in the blueprints. This means that if a resource is added to such a component locally, it will be lost to the content of the blueprint at rollout.

To support the nesting of components such that locally added components are maintained in a rollout, the component must be declared as a container. As an example, the default parsys is declared as a container so it can support locally-added content.

 

https://experienceleague.adobe.com/en/docs/experience-manager-65/content/sites/administering/introduction/msm-best-practices#components-and-container-synchronization 

Arun Patidar
    S
    Shaheena_SheikhAuthor
    Level 6
    November 20, 2024

    Hi @arunpatidar ,

    Thanks for your response. I see the issue is only happening when the Day CQ RolloutManagerImpl configuration has uncheck value for Handle Conflict checkbox.

    On keeping this checked, the issue is resolved. But I am trying to understand what is the impact/functionality of having this checked/Unchecked.

      arunpatidar
      Community Advisor
      arunpatidarCommunity AdvisorAccepted solution
      Community Advisor
      November 20, 2024

      Hi @shaheena_sheikh 

      You can refer below document to check the impact of handle conflicts

      https://experienceleague.adobe.com/en/docs/experience-manager-65/content/sites/administering/introduction/msm-rollout-conflicts 

      Arun Patidar
        Terms & ConditionsAccessibility statement

        Loading footer...