Jump to content
Jest

Selector error depending on order of selector

Recommended Posts

Hi all,

today I've run into some strange error when using selectors. The following selector works fine:

$pages->find('template=TemplateName, (many|of|different|fields*=Searching), (year=Searching), (year>=1941, year<=1960), author*=unknown, publisher*="two, maybe three words"|unknown|"another two, maybe three words", area*=All');

Whereas this one throws an error:

$pages->find('template=TemplateName, (many|of|different|fields*=Searching), (year=Searching), (year>=1941, year<=1960), author*=unknown, publisher*="two, maybe three words"|unknown, area*=All');

The only difference is in publisher field having only two values. The error is Exception: Unknown Selector operator: '' -- was your selector value properly escaped?

 Additional info:

  • ProcessWire 3.0.62
  • All values are sanitized using $sanitizer->selectorValue(string)
  • publisher value usually has commas or parenthesis
  • publisher="one, two"|"three, four" works
  • publisher="one, two"|three|"four, five" works
  • publisher="one, two"|five doesn't work
  • publisher=five works

The only conclusion I can make is the selector fails when the last value of publisher is a single word. Any thoughts?

All help is greatly appreciated!

Jan

Edited by Jest
added PW version

Share this post


Link to post
Share on other sites

I checked the behavior, and i cannot reproduce it with the following code:

$pages->find('template=project, title*="two, maybe three words"|unknown, longtext!=blubb');

 and it works like a charm... (using Dev Version: 3.0.92)

Share this post


Link to post
Share on other sites

That's interesting - your code doesn't work for me.

The same error Exception: Unknown Selector operator: '' -- was your selector value properly escaped? is shown. If I add another value to the title field (title*="two, maybe three words"|unknown|"another unknown") it works until the longtext part. There it shows an error Exception: Field does not exist: longtext. But if I remove the longtext selector and run this:

$pages->find('template=project, title*="two, maybe three words"|unknown');

It still doesn't work.

Is it possible my hosting environment is the reason for this??

Share this post


Link to post
Share on other sites

@Jest does the following works instead?

$pages->find("template=project, title*='two, maybe three words'|unknown");
//or
$pages->find('template=project, title*=\"two, maybe three words\"|unknown');

 

  • Thanks 1

Share this post


Link to post
Share on other sites

Now here's the funny thing: if I wrap the single word value in quotation marks it works.

So this doesn't work

$pages->find('template=project, title*="two, maybe three words"|unknown');

But this does work

$pages->find('template=project, title*="two, maybe three words"|"unknown"');

I've managed to make my code work by checking the number of words in a selector value and if there's only one word I wrap the value in quotation marks.

But it still bugs me why it doesn't work without quotation marks. I'll dig deeper and post the findings, if there will be any.

And thank you guys for your contributions!

Share this post


Link to post
Share on other sites
2 hours ago, Jest said:

There it shows an error Exception: Field does not exist: longtext. But if I remove the longtext selector and run this:

The Field longtext is in my dev installation ;) its just a fieldname created by me

but you can test it with the current dev Version (the dev Version will be the the Master Version in „some“ Weeks (?))

  • Thanks 1

Share this post


Link to post
Share on other sites
6 hours ago, Jest said:

The only conclusion I can make is the selector fails when the last value of publisher is a single word. Any thoughts?

It's a known issue that was fixed in 3.0.80.

  • Like 4
  • Thanks 1

Share this post


Link to post
Share on other sites

@zoeck Yep, I realized why the longtext is causing error... right after I posted the reply :huh: As @BitPoet stated the current dev version fixes this bug, but I'm going to stay on master 3.0.62 since the site will probably be in production sooner than the current dev will become master (and I've found the solution).

@Macrura Thanks for suggestion, the code is cleaner using the selector array but it still doesn't work - as expected due to the bug.

@BitPoet Many thanks for giving me the closure! :rolleyes: Now I'll be finally able to sleep ;)

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 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. For your convenience you can copy/paste a bookmark string from the note at the bottom of the Lister Selector results.
      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'); // Define selector $selector = "template=foo, title%=bar"; // Define columns (optional) $columns = 'title,modified'; $pls_link = $pls->getProcessPage()->url . '?bm=' . $pls->urlSafeBase64Encode($selector . ':' . $columns); echo "<a href='$pls_link'>My link</a>";  
      https://github.com/Toutouwai/ProcessListerSelector
      https://modules.processwire.com/modules/process-lister-selector/
    • 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 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...