Jump to content
Whistletoe

Page selector getting users with specific role

Recommended Posts

Hello everyone!

My first post here. I found Processwire a while ago and have recently been getting to know the system. So far i like it a lot.

Right now i'm trying to make a "page"-field where an admin can select and attach users with a specific role. I can get a list of all users, and filter by different fields, but i don't know how to access the roles. As i understand it, selectors can not be used to find user roles, so i wonder if anyone has another approach. I could add a new field to each user with the role names, but that seems a bit awkward.

Thanks in advance!

Share this post


Link to post
Share on other sites

Sure you can.

$pages->find('template=user, roles=editor')

Or same with $users

  • Like 1

Share this post


Link to post
Share on other sites

Ah, thanks a lot for the quick answer!

I tried "role=something" but not "roles" and then i got lost in the documentation...

Now back to work :)

  • Like 1

Share this post


Link to post
Share on other sites
So far i like it a lot.

Well said, because soon you won't like it a lot anymore. You will love it ;)

  • Like 6

Share this post


Link to post
Share on other sites

Just a quick note for future drive-by readers.  For some reason

$users = wire('pages')->find("template=user,roles=buyer,sort=email");

didn't work for me, but

$users = wire('users')->find("template=user,roles=buyer,sort=email");

did.  Not sure why.

  • Like 1

Share this post


Link to post
Share on other sites

Just a quick note for future drive-by readers.  For some reason

$users = wire('pages')->find("template=user,roles=buyer,sort=email");

didn't work for me, but

$users = wire('users')->find("template=user,roles=buyer,sort=email");

did.  Not sure why.

Both work here - what version of PW are you running?

One thing to note though is that you shouldn't be overwriting $users as this contains all users in the system. If you redefine it, you won't have access to all users via $users further down in your code.

  • Like 1

Share this post


Link to post
Share on other sites

i can verify that the "users" template doesn't work the same way as regular templates:

  • i have a "student" role
  • when i put "roles=student" as the custom selector, the field seems to work perfectly: it shows all users with the "student" role, and shows nobody else
  • however, when i'm trying to save the page, i get this message: Error saving field "student" - Page 1017 is not valid for student

if i use custom php (when of course i can't use autocomplete) it works perfectly with all of these:

  • return wire("users")->find("roles=student");
  • return wire("pages")->find("roles=student");
  • return $pages->find("roles=student"); // which, incidentally, is the same that the custom selector is supposed to resolve

in short, it must be something about the custom selector validation code; if i find some time i'll look some more into it

  • Like 1

Share this post


Link to post
Share on other sites

Hi I was wondering if there's a workaround for this?

I created a new field called blog_author which is a page field. 
It has a selector of "'template=user, roles=editor".

When I try and save down a blog post that has the new blog_author field in it, it's returning the following error.

Error saving field "blog_author" - Page 1415 is not valid for blog_author (Page 1415 does not match findPagesSelector: template=user, roles=blog-author)

I can see the blog authors and select one without errors.

The error occurs when I'm saving.

Have tried to make the template type a basic page field type (instead of user) , but it returns the same error.

Share this post


Link to post
Share on other sites

After much searching, it looks like I needed a *= operator instead of = for Roles? AAArgh  ...

i.e. Not roles=blog-author but roles*=blog-author.

https://processwire.com/talk/topic/10628-error-saving-page-fields/

Seems a bit inconsistent on how Selector is supposed to work, at least going by the examples & documentation I've seen.

Share this post


Link to post
Share on other sites

No not *. If as custom code for a page select you need to use role id.

  • Like 2

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Peter Knight
      Hey I'm building my first new site in well over a year and am a little rusty on selectors but particularly retrieving sub-fields of selected pages.
      I am trying to output the meta data of a blog post as follows.
      [Person Name] is just a field with a Page Reference and simple enough.
      [Job Title] is the sub-field within the page that was referenced above.
      I actually have it working with the following:
      Posted by: <?php if($page->insight_author) { echo $page->insight_author("<a href='{url}'>{title}</a>");} ?> , <?php $roles = $page->insight_author; foreach ($roles as $role) { echo "{$role->staff_role}";} ?> but was wondering how to do this with selector sub-selectors instead. My current code is probably quite 'old school'?
      Thanks
       
    • By theoretic
      Hi there! And thanks for Processwire!
      I have an interesting task which i cannot fulfill as i want. Maybe someone could help me please?
      Let's imagine a simple page structure of this kind:
      Category 1
      + Item 1.1
      + Item 1.2
      Category 2
      + Item 2.1
      + Item 2.2
      My task is to attach some items to more than one category, at least to show some items on different frontend category pages. With PW, it's a piece of cake. I've just created a field called Items (of type Page Reference) and attrached it to Category template. Since i have lots of items inside each category i preferred to use Page Autocomplete input for my Items field. The pages available for autocomplete are restricted by a very simple selector:
      template=item
      It works like a charm. But later i decided to make this autocomplete even smarter and to exclude current category children items from it. I tried to update my selector this way...
      template=item,parent!=(page)
      ...and oops, this broke my selector. My autocomplete founds nothing. Sorry, i had to replace the square braces by () because of this forum limitations, i swear i'm using square brackets in real-life selector!
      What am i doing wrong? And is there any way to include current page info in autocomplete-related selectors? Thanks in advance!
       
    • By Robin S
      Lister Selector
      A Process module that uses Lister/ListerPro, but with a selector string input instead of the normal InputfieldSelector filters.
      Features
      For power users, typing a selector string is often faster and more intuitive than fiddling with InputfieldSelector. It also lets you copy/paste selector strings that you might be using somewhere else in your code.
      Allows the Lister rows to be sorted by multiple fields (not possible in Lister/ListerPro)
      Allows the use of OR-groups (not possible in Lister/ListerPro)
      If ListerPro is installed you can run ListerPro actions on the listed pages - the available actions are defined in the module config.
      Bookmarks can be configured in the module config and accessed via the flyout menu for the module page.
      Usage
      Type your selector string on the Selector tab. The selector is applied when the "Selector string" field is blurred, so hit Tab when you have finished typing your selector.
      Unlike Lister/ListerPro, you can't sort results by clicking the column headings. Control the sort within the selector string instead.
      Superusers can jump to the module config (e.g. to create a bookmark) by clicking the cog icon at the top right of the module interface.
      The module is mostly intended for use by superusers, because in most cases site editors won't understand the ProcessWire selector string syntax. If you want another role to be able to access Lister Selector then give the role the "lister-selector" permission. Only superusers can define bookmarks because in ProcessWire module config screens are only accessible to superusers.
      Screenshots
      Process page

      Module config (when ListerPro is installed)

      Advanced
      If for any reason you want to create dynamic bookmark links to Lister Selector for a given selector you can do that like this:
      /** @var $pls ProcessListerSelector */ $pls = $modules->get('ProcessListerSelector'); $selector = "template=foo, title%=bar"; $pls_link = $pls->getProcessPage()->url . '?bm=' . $pls->urlSafeBase64Encode($selector); echo "<a href='$pls_link'>My link</a>";  
      https://github.com/Toutouwai/ProcessListerSelector
      https://modules.processwire.com/modules/process-lister-selector/
    • By ottogal
      Hello all,
      using PW 3.0.148 with the regular site profile for a blog, I got an an empty pagination output when I had a Toggle field in the selector.
      The Toggle Fieldtype was introduced with https://processwire.com/blog/posts/pw-3.0.139/ .
      The selector resulting in empty pagination:
      $posts = $pages->find("parent=blog, sort=-date, limit=10, toggle_field=0"); It worked well, when I replaced the Toggle field with a Checkbox field:
      $posts = $pages->find("parent=blog, sort=-date, limit=10, checkbox_field=0"); So the prerequisites for the pagination to work are given.
      The settings for the Toggle field were:
      Formatted value: Integer Label Type: Yes/No Input Type: Toggle buttons Default selected option: No Thanks for any hints!
    • By snck
      Hi there,
      I have a problem constructing a selector that finds all pages that refer to pages with a specific template.
      I have pages using an event template and I want to show events based on a specific context. In this example I want to filter the results and only show event pages that relate to a specific template (exhibitions) in their page field related_pages.
      What I tried:
      $events = $pages->find("template=event, related_pages.template.name=exhibition"); Unfortunately it does not work (0 results).
      Same with this:
      $events = $pages->find("template=event, related_pages=[template.name=exhibition]"); At the moment I am helping myself with the following lines, but I have a strong feeling that there is a more efficient solution:
      $events = $pages->find("template=event"); foreach($events as $event){ if(!count($event->related_pages->find("template=exhibition"))){ $events->remove($event); } }  
      I really hope that one of you can help me out.
      Thanks in advance!
      Flo
×
×
  • Create New...