Recently Browsing 0 members
No registered users viewing this page.
By Kiwi Chris
I have a role that has page edit, view, and clone permissions on a specific template.
If a page using the template is locked by a user in a role with lock/unlock permissions on the template , the only button alongside it in the page tree is view, for users who don't have lock/unlock permissions.
If however, I also give the role page-lock permission on the template, they then get additional buttons, edit, copy, and unlock.
I don't actually want to give this role unlock permissions, but I do want the copy (clone) button to display alongside the page in the page tree.
Elsewhere, I've discussed how I've worked out how to create a hook to unlock the copy, but I want to keep the original page so a user without lock permissions can't unlock from the page tree it to make changes.
Question: What method should I hook into to intercept any attempt to change the lock status?
this maybe a simple question, but it bothers me for a while now:
There used to be a warning, if two or more user try to edit the same page. But ever since AdminThemeUIkit I haven't seen it any more.
Is this a bug or are there special circumstances under which the warning will be displayed?
If I am logged-in in the same browser with one default and one privat window, I don't see this warning. But also different browsers on different machines in the same network don't see this warning.
I was looking for the blog post on which this feature was announced, but couldn't find it anymore.
We had the case, that two people were writing a text for the same page, but after person A saved the page first, the text of the person B was lost. I know we could have used ProDrafts for this case, but it shouldn't happen in the first place.
I would appreciate some feedback. 😀
I try to add page-edit-own and page-delete-own permissions, but it's strange...
If a add the custom permissions it looks like both are children of page-edit respectively page-delete. I played with added / revoked permissions, but I can't get it work, that a user of a role just can delete own content.
First the user can't delete any content and now the user can delete own and foreign pages 🤪
Is there a tutorial to learn more about the PW permissions?
Or do I have to rename the permissions to page-own-edit and page-own-delete to be independent from page-edit and page-delete?
I have a website that allows users to create their personal "website" (a page with sub-pages).
Users shall be able to:
Log in (frontend and/or admin), Edit "their" page(s) - I am using the "Page Edit Per User"-module (https://modules.processwire.com/modules/page-edit-per-user/) to grant access to the relevant pages Create child pages - possible? Users shall not be able to see other pages in the admin interface - "Admin Restrict Page Tree" may do the trick (https://modules.processwire.com/modules/admin-restrict-page-tree/)? Frontend editing shall be possible - I am considering "Fredi" (https://modules.processwire.com/modules/fredi/) for this. The challenge is that it takes a lot of modules and configuration.
Is there a way to set this up that doesn't require a lot of configuration for each new user?
not sure why but PW adds any uploads as permissions 600 (e.g. images wont load after upload unless i go in with the same server user and change permissions to 755 or similar). This ever happened to any one else?