Search the Community
Showing results for tags 'page-edit'.
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)
"Permission “page-sort” for template “ ... ” not allowed (requires “page-edit” permission)" – This lovely error message is thrown at me, if, as implied by it, I try to add (to my "editor" role) the permission "page-sort" for a specific template, without the permission "page-edit" enabled for the same template. Seems like it's been mentioned a few times before but never properly answered, by e.g. @Robin S ... : "Allow the granting of page-sort permission independent of page-edit": https://github.com/processwire/processwire-requests/issues/29 Why do I wanna do this?: I have a page tree structure 🌳 as so: ________________________ Category [C1] – Page a [C1_p] – Page b [C1_p] Different category [C2] – Page c [C2_p] – Page d [C2_p] ________________________ The page "Category" has the page-template "C1", the pages "Page a" and "Page b" both have the page-template "C1_p". The page "Different category" has the page-template "C2" the pages "Page c" and "Page d" both have the page-template "C2_p". The two pages called "Category" and "Different category" do not have any content, they only serve as containers for pages belonging to that category. I want my "editor" role not to be able to do anything at all with these pages "Category" and "Different category"; i.e. I do not want my editor to be able to edit, move, unpublish, hide, lock, delete (or do anything else to) these category pages. – So, I want my "editor" role to have the "page-edit" permission for pages with the templates "C1_p" and "C2_p", but not for the pages with the category templates "C1" and "C2", Also, I want my "editor" role to be able to move the pages with the templates "C1_p" and "C2_p" within their parent-pages. Problem: But if I just simply add the "page-edit" and the "page-move" permissions for the "C1_p" and "C2_p" templates, then, using the "editor" role, I am not able to move these "C1_p" (and "C2_p") -template-based pages. I can actually click "MOVE" next to them and then move them, but... then I will be met by the error message "You do not have permission to sort pages using this parent - /Category/". – So, I try to add the "page-sort" (description: "permission to sort child pages") permission to the "C1" and "C2" templates... but then trying to do so I am met by the initially mentioned error message ! Permission “page-sort” for template “C1” not allowed (requires “page-edit” permission) . And, as mentioned, I do not want my editor role users to be able to edit these category ("C1" and "C2") pages... – what to do about this? 😅 All the best, Jonatan
In one of my templates, I have divided my fields into 5 fieldsets. The default tab now only appears when you create a new page. Once saved, you only see the custom 5 tabs. Now my problem is: When you open a page with such a template, it still jumps to the 1st tab (which is hidden by custom CSS). How can I achieve that it shows another tab? Would I have to write a hook? Some sort of redirect? e.g. I want to open the "Projekt" tab, so I don't get to see an empty page with just the save-button, when opening a page using that template.