Skip to main content
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
leeaslingAccepted solution
Level 8
May 10, 2016 12:55 PM UTC

We still see the issue with every new instance of AEM 6.1 we start.  I have a package that i took from another instance that contains the tree activation page.  If you shoot me a private message, i can forward the package over to you.

15 replies

Level 4
Jul 25, 2016 5:11 AM UTC

Hi Ashok,Could you please share the list of filters that need to make this available?

Translate
Sep 15, 2016 6:22 PM UTC

Just to confirm the solution explicitly to those who are seeing this (as I did) - the root cause is that /etc/replication is missing the 'treeactivation" folder. If you export/import from a working 6.1 instance (or simply recreate the folder in CRX with correct props), the problem goes away.  See attached screenshot for desired state in JCR.

Translate
Adobe Employee
Sep 16, 2016 3:45 AM UTC

You are right in observing this. Apologies for hitting a known issue.

CQ-45211 - "Activate Tree" is not shown on the instance with nosamplecontent run mode

Workaround is pretty straightforward for it: manually create the missing node at /etc/replication/treeactivation:
{
jcr:primaryType: "sling:Folder",
jcr:title: "Activate Tree",
title: "Activate Tree",
sling:resourceType: "cq/replication/components/treeactivation"
}


This will solve the problem.

Translate
chirran414
Level 4
Feb 9, 2019 12:05 AM UTC

Does anybody have a complete solution/know that this issue got solved in later versions (AEM 6.3.3) ?

Translate
joerghoh
Adobe Employee
Adobe Employee
Feb 9, 2019 5:51 PM UTC

localhost:4502/libs/replication/treeactivation.html is available on my local AEM 6.4 SP2

Translate