I have created an editable page template under Tools > General > Templates.
On this template within the Layout Container [Root] I have added a component in Structure mode which I have populated with content. The idea is that this component populated with content will show on all pages that implement this template.
However, whilst this displays correctly in author, on publish the component does not show on the page. I have worked out that this is because the anonymous user does not have read permissions to the /conf/.../templates folder.
Am I using editable templates in the wrong way, or do I really need to give read permissions to the /conf/.../templates in publish (I am very reluctant to do so)?
Solved! Go to Solution.
Views
Replies
Total Likes
Hi,
/conf/ access is not required at publisher, it is access internally by script user/service.
Have you deployed/publish the content and code in publisher after changes.
Can you try with Core component project or WKND project
Hi,
/conf/ access is not required at publisher, it is access internally by script user/service.
Have you deployed/publish the content and code in publisher after changes.
Can you try with Core component project or WKND project
Views
Replies
Total Likes
Views
Replies
Total Likes
Views
Replies
Total Likes
Views
Replies
Total Likes
Arun - just to clarify, my understanding is the anonymous user is part of the everyone group. So when I say I don't want to give the anonymous user permissions to my project's /conf/.../templates folder on PUBLISH, this also means I want to avoid giving the everyone group permissions to this folder on PUBLISH - as the result is the same.
Views
Replies
Total Likes
Hi,
In PUBLISH everyone group should have read permission to read template section inside /conf/.
anonymous user is member of everyone group, so no need to add explicit read permission for anonymous user.
I would say, check below permission in PUBLISH :
1. anonymous user is added in everyone group
2. everyone group has read permission at /conf/...../myproject
It is fine to give /conf/ permission but direct access of /conf/ should be blocked from dispatcher.
Views
Replies
Total Likes
Views
Replies
Total Likes