Most probably the launcher condition is not getting triggered. Setup a DEBUG logger on the following class to get more info:com.adobe.granite.workflow.core
- Can you compare all the properties of a working and non-working page?- Check if the page is under a particular hierarchy that a user does not have access to?- Go to "http://<host>:<port>/crx/explorer/ui/aceditor.jsp" and compare the permissions of a working and non-working page.
Can you check if the group has replicate rights on the content directory?Also, As per the repository restructuring for 6.4[1] and above,/etc/workflow was moved under /conf and you might need provide the following nodes with proper rights:/libs/settings/workflow/models/conf/global/settings/workflow/m...
Yes, the reference rail will show the links you reference within the components. The example below from my local instance :- Opened a page named "/content/we-retail/us/en/experience/arctic-surfing-in-lofoten.html"- Added an RTE component to the page and then a link to "/content/we-retail/ca/en/men.h...
I believe you need to use the Reference Component under the General Category in order for references to show up in the left pane.I tested this on my local instance and using the reference component works as expected.
Sorry, I misread the version number, if you are using 6.2 that's the correct article you are following.There might be an issue with the Keystore.Can you try to recreated the keystore.Also, check if "cryptoservice" user has jcr:all rights on /etc/key