Search the Community
Showing results for tags 'restrict'.
Found 4 results
-
Hi friends! And thanks for Processwire 😉 I have a specific question about PW admin. There's a typical situation when content editors need access to the public page tree only. Ideally, such users should not have the top PW admin menu (Pages, Setup etc.) at all, same for the Admin branch in page tree. Developer users should have everything concerning development (Setup, Modules, maybe Access...) but the public page tree can be limited/restricted for them. It's pretty like how the Admin Restrict Branch module works. But different. Admin Restrict Branch only allows to select a single branch which will be available for certain users. And I'm not sure the ARB will affect the top menu. Is there an existing solution for my request? Or maybe it's time to think about extending the ARB functionality? Many thanks for any possible advice. -
Hi, have a site where I set up a news category, then under that I have different regions where editors in those regions can add news stories. I'm trying to figure out how to allow each editor to only add/edit stories in their region, and not allow editors from other regions to edit them. example: News (template:news-category) Washington County (template:news-region) My First News Story for Washington County by Editor 1 (template:news-article) Jefferson County (template:news-region) A News Story by the jefferson county editor (template:news-article) Taylor County (template:news-region) A news story by a Taylor county editor (template:news-article) I really don't want to create 3 different news-region templates along with 3 different news-article variations, and 3 different types of Editor roles. Is there a way / module that will let me say, "jane which is an editor can only add and edit to Washington County" and "bill which is an editor can only add or edit to Taylor County", etc? Also, it would be nice to allow the "home office" editor to add/delete/modify contents created by the other editors, a "Super Editor" if you will. Thanks mucho!
-
Hello, I'm facing an issue trying to restrict access to a field so front-end edition is possible in an easy manner for the user. Let me explain : I have a field 'group' which is a Page list of group names. I want the user to be able to front-end edit a 'player' page in which this group field appears. I'd like the user to have a list of groups limited to his or her own groups (so he or she doesn't see all groups created by other users). In the back-end, I use this selector string : template=group, created_users_id=[user], sort=title This works great ! BUT here's my issue : If I back-end edit a 'player' page as 'Admin', the 'group' is empty (since admin is not the created-users-id and the group field is then empty... In other words, I must choose between all groups shown to all users (which may be scary for a user having only 2 or 3 groups whena list of 60 shows up) OR having a correct list for the front-end user, but empty for the back-end 'admin'. Can anyone think of another way I could get the expected result ? I have a feeling the simplest way would be to have a "Ignore for superusers" checkbox next to the 'selector string'. Thanks ! -
Hi there, just looking for ideas for an IP restricted login page for employees on site? Where to start? Is the IP restricted idea best? Just basically want to make sure employees are in the building when they sign in. Thanks for any help.
