"Permission “page-sort” for template “ ... ” not allowed (requires “page-edit” permission)"
By
jonatan, in API & Templates
-
Recently Browsing 0 members
No registered users viewing this page.
-
Similar Content
-
By SwimToWin
I have a nested page structure that fails for users without superuser permissions:
Works for superusers / non-superusers:
- foo
-- bar
--- page (status: published)
---- page (status: published)
--- page (status: published)
Fails for non-superusers (Works for superusers):
- foo
-- bar
--- page (status: published)
---- page (status: published)
--- page (status: unpublished <- apparently the template structure fails when there's one unpublished page)
Template:
<?php foreach ($page->children('include=all') as $p): #Fails for non-superusers ?> <?=$p->render()?> <?php endforeach; ?> a) Works for non-superusers when I grant Page Edit permissions (on the template) to their assigned role/s.
b) When I remove 'include=all' or 'include=unpublished' then it also works for non-superusers:
<?php foreach ($page->children() as $p): #Works for non-superusers ?> <?=$p->render()?> <?php endforeach; ?> Error message (non-superusers)
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Error has been logged.
/www/site/assets/logs/errors.txt
/foo/bar/baz/ Error: Exception: Page '/foo/bar/baz/quz/' is not currently viewable.
/www/site/assets/logs/exceptions.txt
/foo/bar/baz/ Page '/foo/bar/baz/quz/' is not currently viewable. (in /wire/modules/PageRender.module line 410)
Debug (non-superusers)
Error: Exception: Page '/foo/bar/baz/quz/' is not currently viewable. (in wire/modules/PageRender.module line 410)
#0 wire/core/Wire.php (397): PageRender->___renderPage(Object(HookEvent))
#1 wire/core/WireHooks.php (823): Wire->_callMethod('___renderPage', Array)
#2 wire/core/Wire.php (465): WireHooks->runHooks(Object(PageRender), 'renderPage', Array)
#3 wire/core/WireHooks.php (924): Wire->__call('renderPage', Array)
#4 wire/core/Wire.php (465): WireHooks->runHooks(Object(Page), 'render', Array)
#5 site/templates/template.php (191): Wire->__call('render', Array)
-
By snck
Hey there,
for a client website I need to implement a "reviewer" role. "Reviewers" should be able to review new (unpublished) articles to give feedback to editors, but not have the permission to change them.
I built a new "reviewer" role that only has page-view permissions for the respective templates, but this permission does not include viewing unpublished pages. How can I grant them access to the unpublished articles without giving them page-edit permission?
Cheers,
Flo
-
By AndZyk
Hello,
I have a user role employee with the permission page-edit-created. This user role has access to add new pages to the template posts with the template post.
The template posts should have children with the template post. The template post should have the parent with the template posts. Now every time I try to add a new page with the template post, an exception throws:
You don't have access to the template required to add pages here
Is this a bug in this permission or have I not configured the permissions correct?
Is there a hook to allow to add pages to the template posts for the role employee?
I would appreciate some help. 😀
Regards, Andreas
-
By snck
Hey,
I want my editors to be able to use the page lister, especially the bookmarks. I added the page-lister permission to the editor role, but Page lister ("Find" menu item) does not show. Is there anything else I have to do? Links to bookmarks work for the editors, but I would be glad to show them the menu item as well.
Maybe this has something to do with the long history of the site (started with ProcessWire 2.4 and upgraded to 3.0.148 over the years)?
Thanks,
Flo
-
By snck
Hello,
for a project I have pages with different “content areas“ that can be edited only by specific user roles. In the past I setup a fieldset (tab) containing all the fields that should be available to only one specific group of users and set the fields' view and edit permissions (in the Access tab) accordingly. The result was as expected: Users assigned to the specific role could see the tab, click on it, edit content, users without the role could not see the tab. After updating this installation to 3.0.148 yesterday I wanted to setup another tab following the same principle, but I have no "Access" tab for the fieldset to limit access to the specific role. I even tried cloning an existing (and still working) fieldset. The existing fieldset has some template overrides (screenshot attached) that lead to the desired behaviour, but I am not able to reproduce these settings because there is not "Access" tab for my fieldset in template context either.
Is this a bug in 3.0.148? Has the fieldset fieldtype changed? Am I missing anything here?
I am glad to hear from you guys.
Cheers,
Flo
-
