Not able to add mixin "mix:versionable" in page nodes | Community
Skip to main content
Ankan_Ghosh
Ankan_Ghosh
Level 3
January 13, 2025
Solved

Not able to add mixin "mix:versionable" in page nodes

  • January 13, 2025
  • 3 replies
  • 740 views

I faced an issue where jcr:uuid is not generated if we publish a page using manage publication, but not if we publish using quick publish. Upon investigation, we discovered that when we publish using quick publish, "mix:versionable" is added to the jcr:mixinTypes property. As a solution, I am trying to add a replication event handler that will add this "mix:versionable" mixin to the jcr:content node of the page if the property is not present. I am unable to add the mixin as I get an exception "org.apache.jackrabbit.oak.api.CommitFailedException: OakAccess0000: Access denied".

 

Is there any to add this mix:versionable mixin to the node? If there is no way to add the mixin, I will add a custom ID upon page creation but that will require a lot of changes as we have already referenced jcr:uuid for our previous solutions. So, if anyone is aware of how to add this mixin, please provide some insights.

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 @ankan_ghosh 

The mix:versionable  is added to page with quick publish because of new version of page is created, if you can also create a version.

 

Otherwise the way you are trying might work but check the permission.

Permissions : jcr:modifyProperties, jcr:nodeTypeManagement, jcr:write 

 

Node node = session.getNode("/path/to/your/node"); if (!node.isNodeType("mix:versionable")) { node.addMixin("mix:versionable"); session.save(); }

 

 

 

3 replies

arunpatidar
Community Advisor
arunpatidarCommunity AdvisorAccepted solution
Community Advisor
January 13, 2025

Hi @ankan_ghosh 

The mix:versionable  is added to page with quick publish because of new version of page is created, if you can also create a version.

 

Otherwise the way you are trying might work but check the permission.

Permissions : jcr:modifyProperties, jcr:nodeTypeManagement, jcr:write 

 

Node node = session.getNode("/path/to/your/node"); if (!node.isNodeType("mix:versionable")) { node.addMixin("mix:versionable"); session.save(); }

 

 

 

Arun Patidar
    Ankan_Ghosh
    Ankan_GhoshAuthor
    Level 3
    January 17, 2025

    The problem was with the permission. After giving all the required permissions, I was able to add the mixin. Thanks! 

    Uppari_Ramesh
    Uppari_Ramesh
    Level 5
    January 14, 2025

    Hi @ankan_ghosh , @arunpatidar 

    By default AEM replication agents creates a version of page when you replicate the content. During version, AEM puts the node in checked in state so that no other operation will be done on that node. You can try checkin and checkout methods present in below API reference.

     

    https://developer.adobe.com/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/javax/jcr/version/VersionManager.html#checkin(java.lang.String) 

     

      AmitVishwakarma
      Community Advisor
      AmitVishwakarmaCommunity Advisor
      Community Advisor
      January 19, 2025
      o resolve the issue with adding mix:versionable:

      Check Permissions: Ensure the user has the required permissions to modify the node and add mixins.
      Use System User: If permissions are restricted, use a system user with appropriate rights.
      JCR API: Use the JCR API to add the mixin:

      Node pageNode = session.getNode("/content/myPage/jcr:content");
      if (!pageNode.isNodeType("mix:versionable")) {
      pageNode.addMixin("mix:versionable");
      pageNode.save();
      }

      Check Node Restrictions: Ensure the node is eligible to have the mixin.
      Custom ID: If adding the mixin isn't feasible, consider using a custom ID, though it requires more changes.
        Terms & ConditionsAccessibility statement

        Loading footer...