Jump to content

Search the Community

Showing results for tags 'roles'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Welcome to ProcessWire
    • News & Announcements
    • Showcase
    • Wishlist & Roadmap
  • Community Support
    • Getting Started
    • Tutorials
    • FAQs
    • General Support
    • API & Templates
    • Modules/Plugins
    • Themes and Profiles
    • Multi-Language Support
    • Security
    • Jobs
  • Off Topic
    • Pub
    • Dev Talk

Product Groups

  • Form Builder
  • ProFields
  • ProCache
  • ProMailer
  • Login Register Pro
  • ProDrafts
  • ListerPro
  • ProDevTools
  • Likes
  • Custom Development


There are no results to display.

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 49 results

  1. I'm working on a site that has 12x languages (and 12x translators) and following on from working out how to create roles that only allow editing of one language, the client have requested that these translators be able to edit at the same time. What are the possibilities here with Processwire? I'm thinking (potentially) 12x users editing the same page is a nightmare of overwritten changes etc. Has anyone had any similar requests from clients for multiple users editing at the same time? I think the solution may need to be 12x languages manually added so the page tree is: Home - English -- Articles --- Article title --- Article title - Spanish -- Articles --- Article title --- Article title - French -- Articles --- Article title --- Article title etc However I'd prefer not to do this as it's *a lot* of duplication and also not using the inbuilt language options of Processwire. Any help/thoughts on the best way to tackle this much appreciated.
  2. Hi, does anyone encounter the Same bug ? 1.i have multiple pages in PW 2.5.29 2.and some older ones i need to Upgrade from 2.5.21 in Case 1 as a Superuser i cannot change stuff in my Profile (e-mail / password / language do work, some custom fields dont (also roles doesn't)) in Case 2 as a Superuser i can change everything without a sweat. Greetings
  3. Hello there, I'm struggling again with a new site I'm trying to implement for fun. First, for personal use, but now I'd like to make it a 'member available' site. The site is just an invitation management site : who came over? What did they eat? What ere the recipes? And so on... Here's my problem : I'm trying tp use Fredi (the module) to allow members to edit their recipes, their hosts, their profile. Actually, I wanted to use Fredi so I didn't have to really care about anything front-end. Fredi would take care of it. I added a 'member' role (with page-edit access) to each member. It works fine this way, but the worry I'm facing is that if a member manually adds '/processwire' in the address bar, he will have access to all the members list and invitations and I wish I could hide all of this. Actually, they can't 'View' or 'Edit' anything, so I guess the probability of them fiddling with all these information is close to zero, but I do'nt like it anyway. I wish they could have access ONLY to their stuff. In my tree, this means everything under '/invitations/user-id', 'guests/user-id/', and '/dish/user-id'. And I'm unable to find out how to do this... Hence my post The other way I imagined : leaving all members with 'guest' role (if they type 'processwire' in the address bar, they won't see anything (which is good), and implementing front-end editing solutions for the members. It could work, but I feel like I'll never use the user/roles PW capabilities if I start working this way Am I misunderstanding something? If anybody could give me a clue about how to handle this issue, I'd appreciate
  4. So far I have seen that you can only allow superuser to manage roles, however I don't need the admin of the site managing everything else. I need to add a permission to allow them to add roles if needed and delete roles if needed.. Basically control roles. Any thoughts on accomplishing this?
  5. Hi all. I have pages (templates) that are only accessible to certain users. Now I need to get all users that have view access to specific pages (they will get email when page updates). I thought of something like this: $template = wire('templates')->get($p->template); $roles = $template->getRoles(); $users = wire('pages')->find('template=user, roles=' . $roles); But it looks like getRoles() doesn't returns the roles for that template. Roles is an empty PageArray. What is wrong or is there another way to get those users?
  6. Hello together, this is my first post in this forum. I like to do the following: I have some users, let’s say 20-30 people that should only be able to edit their own pages. By using the "Page Edit Per User" module it’s mostly working in this way, that the user can edit his own page, okay. The problem is, that the user must be given the rights to add children pages, edit and sort them in the page tree inside "his" main page and it seems that the "Page Edit Per User" module is just limited. Let me give you an example. I have the following tree: Home Page 1 - Children 1.1 - Children 1.2 - Children 1.3 Page 2 - Children 2.1 - Children 2.2 - Children 2.3 . . . So, I also have two users: User 1 and User 2. User 1 needs to be the following rights: Edit, Delete, Move all children pages for Page 1 all other actions are not allowed. So, User 1 can NOT delete his main page, Page 1 or any other page "outside" Page 1. Any ideas on how to solve that? Thanks so much in advance for your ideas. -Thomas
  7. I'm playing around with permissions for THE FIRST TIME and I'm quite excited about the whole thing because when I log in as this other role I made I realize how much cleaner it looks of course to somebody who isn't developing the site. Anyway I have a template listing that is the default/only created under template listings. (A listing may not have children.) So then I made a role, listing_manager, you know... to manage the listings... granted permission to view, edit, and create them. Problem is, when logged in as the listing manager, I can edit the listings, but there's no "New" link to create any? I guess that's because that link is part of the listings page/template's row/branch, so... it doesn't show for its children though... which are all of the same template where the role does have permission to create. This seems like a silly bug. Any suggestions as to what might be the simplest, cleanest fix for this? or maybe I have something set up wrong? Thanks.
  8. Hi, I've just set up a client area with ProcessWire based on Ryans step by step guide here - It's pretty much identical, client areas are rendered depending on the users name. This means I can only have one login per client since users names must be unqiue. Often there's time where I have multiple contacts for one client and ideally I'd like to create a user login for each person involved. One login per client works, but ideally I'd like a unique login based on their email address. Is there a way to allow users to login using their email address and using a users name more than once? No worries if this isn't acheivable, I'm extremely happy with PW and have been very impressed at how easy it is to use. To all those involved, great work! Cheers
  9. Hi, I have a frontend menu which is built using pages and a page select; it is output using a function that cycles through the pages and creates the menu; for this menu I wanted to also have the ability to select on some menu items which roles can see those items; I made a new field called menu_roles which selects the role; I didn't use built in roles field because it is permanent and i couldn't get rid of it off one of my templates once i added it. When i'm cycling through the pages, i'm using this to check if the current user should see the menu: $menuVis = true; if($child->menu_roles->count()) { foreach($child->menu_roles as $cmr) { $menuVis = true; $cmrRole = wire('roles')->get("$cmr->name"); if (!wire("user")->hasRole("$cmrRole") ) $menuVis = false; } } if($menuVis == false) continue; Edit: this sort of doesn't work... i can't figure out how to check multiple roles against a user at once, to get the visibility variable to be correct...Aarrgh! logic
  10. Hi, in PW 2.4.0 I have setup a role "publisher", containing the permission to Clone a page and Clone a tree of pages. All Permissions for this role: Delete pages Edit pages View pages User can update profile/password Clone a page Clone a tree of pages The user that is being set to publisher should then be able to view and edit, but also clone a page or tree of pages. Within the templates' Access tab, I have selected the publisher role to be able to: VIEW PAGES EDIT PAGES CREATE PAGES ADD CHILDREN Am I missing a "CLONE PAGES" option here? On the family tab, I have set "Can this template be used for new pages?" to "Yes". For some (for me) unapparent reason, I do not have the option to copy a page from within the tree, the button is missing, even though the template and role/user seems to be setup properly. How can I get this to work? Kind regards, Pascal
  11. Hello, I have a similar case like described in bwakad's post. But I don't want to ask there since the post is already marked as solved. My site has users with role "frontend" assigned that can edit their user profiles and add stuff on the frontend. frontend role setup: The user profiles are all stored in pages with template "userprofile" That template has these access settings: All user profiles live under a page "Profiles" that also has the template "userprofile": Now I would expect that the "Profiles" page only appears in the menu when a user with role "frontend" is logged in. But the menu item does not get displayed. I'm also using the function to display bootstrap menu item but bwakad's workaround seems a bit awkward (excuse the pun ). Does PW just work that way or is my access and permission setup wrong somehow? And how do I get the "profiles" menu item displayed only to users with role frontend?
  12. I'm signed-in as admin with guest, superuser roles, but cannot edit any content within Body or Sidebar. This is despite the Access page apparently showing I have permission to do all this. I'm really keen to get started with PW, but this is extremely frustrating.
  13. I successfully created a role with the API: $role = new Role(); $role->name = 'some-role'; $role->save(); It's now there under access/roles/ But when I want to get the role via API, I get a NullPage: $roles->get('some-role'); // or $this->roles->get('some-role'); Please help!
  14. I've a site with different sections. Each user is assigned to a section and each section has an editor. I want those editors to be able to modify the users that are assigned to their section. I tried hooking into ProcessUser::execute but I'm not sure how to filter the 'pages'. $this->addHookBefore('ProcessUser::execute', $this, 'modifyuserpagelist'); In what way am I able to modify the User List?
  15. Hi! Don't need it at the moment, but I'm interested in... Is it possible to set permissions for pages belong to a category? Maybe userGroups (apeisa, forum post here) could be a solution, but it's a early dev stage. Simplest way to build categories should be page references. Categories are pages and will referenced to (content) pages via page reference field. Like blog tags / categories. Content should use the same template. Is there a (easy) way to grant a role view permissions to pages belong to "category A"? For example like forum category/ board or gallery album view permissions to roles? Maybe a workaround/ solution If I build a template for each category I can manage permissions via template access, but I don't really need more than one template apart from permission settings... Use the same template should be done with advanced template setting -> alternate template filename Mentioned by Soma at the topic A different way of using templates / delegate approach
  16. Hi all! if($session->login($username, $pass)) { echo ($user->hasRole('clubmember')==1?"yes":"no"); ....... } The above code snippet prints out "no" at the first login and "yes" at the second login. The user has the role mentioned in the code, so I'm not seeing, what's happening here. Sorry for all my stupid questions, sometimes it's hard to see the obvious(??).
  17. Sorry but i can't set up a new role called 'editor' where i want to this role have permission to edit and create new content to the site; i manage to apply the edit feature with the module "PageEditPerUser" made by ryan but i need to apply the same for create. How can i do this? EDIT: i found this Edit template -> access tab -> and "activate" page view / edit / add child permissions for each roles there. But i need to add acces to each template i have to each roles? Regards,
  18. Hello, Somehow I can't seem to get a new user role to publish new pages -- only create and save unpublished. I created a new role called "editor" with view, edit, delete, and move permissions. I also allowed access management on the appropriate template. Still nothing. What am I missing? I'm using PW 2.2. Knowing how this goes, I'll probably figure this out in a second or two...! Tempting fate, -e.
  19. Hello All, This question is a part of my series of questions that I'm coming up with while building a drama ticket booking/selling website. So for today my question is, I want that only registered users should be able to review(comment) any drama. Others who wish to comment/review the drama should first signup and then add the comment. I've figured this is possible if I add a new permission such as add-review and link to a role (eg, in my case registered is a role). But, how exactly will the system know that add-review refers to adding comments? Which step am I missing here? Or is this not the way to do it? Please, I need some help here. Thank you all in advance.
  20. I understand how to add a field to users (regardless of role), however I would like to add a field that only is assigned to a specific user role. Is this possible? Couldn't find any information about this in the forums or documentation, so I'm resorting here to the forums. Sorry if this is a repeat question.
  21. Hi all, I am creating a site that will have multiple users in ProcessWire and I want to be able to limit the ability to edit pages so users can only edit the pages that they themselves created. I noticed the default functionality allows you to assign roles yet anyone with this role appears to be able to edit whatever pages and templates have access to that role. Thank you for your help!
  22. Hi all, I would like to redirect the session after successful login for a specific role. I want to keep a specific role in the front-end most of the time and upon successful login, would like to redirect them to the front page instead of the Pages section in the back-end. How would you suggest hooking into the login function and redirecting that role upon successful login? I know I'll need to use $session->redirect(). Thanks!
  23. Just trying to get my head around this one and was wondering how you would play it on your sites? I have a property portfolio page with different properties as children. This should be visible to all visitors (no problem here) There also needs to be property-specific extras for people who are logged in as "investors" (role already created) I'm just trying to think hierarchically the best way to go about this. I currently see two options but I'm hoping there are more, or that I'm missing something. Option 1: Create an Investors page and repeat the portfolio children underneath - The downside of this I suppose is that the staff would had to add a property twice and repeat all the content? Option 2: Use same "Portfolio" and "Portfolio-entry" templates and then add permission-only content to these templates such as: <?php if ($user->hasRole("investor") == 1) { ?> // some code here... <?php } ?> This could be a better option but I'm wondering how cluttered the templates may get. Would just be interested in your thoughts on how you may go about this? Thanks!
  24. I don't seem to be able to get any user other than superuser to see a '+ Create New' link: I don't know if I have hit a bug (I doubt it) or a gap in my knowledge (more likely) but I am using a Page field with Input type AsmSelect to allow editors to add existing tags* or make new ones (*tags=pages beneath /tags/). This all works fine and is covered in part here. However I've found that even with a new user set to have all permissions they never see the '+ Create New' link to add another tag (page via AsmSelect). The superuser can see it fine. Has anyone come across this type of problem or suggest something for me to go and look at/read that I may have missed? Thanks in advance for any comments.
  • Create New...