Hi!!
We are using acs commons generic list and it's working fine on author and publisher instance but the list is not appearing on the dispatcher. Please advise.
Solved! Go to Solution.
Views
Replies
Total Likes
Hi @ReddyIshanvi ,
Not sure what's the use case here. Assuming you have a Generic list saved under the path(/etc/acs-commons/lists/), if you are trying to access the list as anonymous user, make sure the anonymous user or "everyone" group has the "read" permissions to your generic list node.
You are saying that you are able to see the list on the publish instance, Are you seeing the list on publish instance without any login(admin or some other user)?
If you are using a service user to access this list via code, make sure you give the service user access on publish instance as well.
Hope this helps.
Thanks,
Sudheer.
Hi @ReddyIshanvi ,
Not sure how are you consuming the list, but you need to check if there is a dispatcher rule to allow requests to the generic list path.
Hope this helps!
Regards,
Nitesh
Please check permissions from AEM publisher to ensure that everyone has access to the generic list folder structure, and if you are trying to get the list via JavaScript requests, you check dispatcher rules, to ensure that the folder structure can be accessible as well.
Hi @ReddyIshanvi ,
Not sure what's the use case here. Assuming you have a Generic list saved under the path(/etc/acs-commons/lists/), if you are trying to access the list as anonymous user, make sure the anonymous user or "everyone" group has the "read" permissions to your generic list node.
You are saying that you are able to see the list on the publish instance, Are you seeing the list on publish instance without any login(admin or some other user)?
If you are using a service user to access this list via code, make sure you give the service user access on publish instance as well.
Hope this helps.
Thanks,
Sudheer.
This happens due to permission on the "/etc/acs-commons/lists" node as mentioned by sudheersundalam . You can provide these permissions either by repo init config files or adding permission to this node manually. Using the repo init config is recommended so that these permissions can be cascaded to the higher environment as well.
Thanks,
Lokesh Tripathi
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies