Jump to content
dragan

not all pages showing up using Page Autocomplete

Recommended Posts

What could be the reasons why not all pages appear in my page referefence field with page autocomplete?

I have a dozen pages that should appear, with a 4-letter string that never show up.

 

My selector should be fine:

parent=1041, template=project, id!=id, sort=vertec, include=all

Where does it actually look for the suggestions? only default page-title? I tried with title and several other fields, also custom variations for the label, e.g.

{vertec}, {title}, {client_name} {year}

Q1: In which fields does PW look for autosuggestions? only title? Can it be configurable to look also elsewhere (let's say 3 text fields)

Q2: Does my custom labeling actually change anything in the behavior of autosuggest? (I guess not)

 

In my case, I have over 1000 pages under one parent. Using the other option "page-selector" is not a real option (paginate several times...)

Share this post


Link to post
Share on other sites
25 minutes ago, dragan said:

What could be the reasons why not all pages appear in my page referefence field with page autocomplete?

Unless it was changed recently, AsmSelect and PageAutocomplete are configured to return 50 results. Could that be the reason why some results not showing up?

  • Like 1

Share this post


Link to post
Share on other sites

You may want to look at the field that has Page Autocomplete as the input and see how it's configured.

page-autocomplete-field.thumb.png.f9358ad4248639e466a48d2681ff7615.png

  • Like 1

Share this post


Link to post
Share on other sites

Wow. I don't even see such a section. I quickly switched to type select, and then I have only one text-input, but I don't see all these search operators. Or "fields to query for autocomplete" :(

PW 3.0.81, btw.

 

page-autocomplete-module-info.PNG

Edited by dragan
added screenshot

Share this post


Link to post
Share on other sites

Alright. If I choose multiple, I get this settings panel as well. 

Why doesn't it appear if I choose single page? o_O

Share this post


Link to post
Share on other sites
14 minutes ago, dragan said:

Alright. If I choose multiple, I get this settings panel as well. 

Why doesn't it appear if I choose single page? o_O

The screen I showed was from going to /Setup/Field and picking the field that has been assigned Page AutoComplete as in input.

Share this post


Link to post
Share on other sites

I know. But if you choose the first page autocomplete in the dropdown + save, operator settings are not shown. 

(grumble... does anyone know how to create a screenshot of an open select menu?)

Share this post


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

grumble... does anyone know how to create a screenshot of an open select menu?

I use PicPick. Open your select menu and then use the keyboard shortcut for tasking a screen grab (region, whole screen, etc)

Share this post


Link to post
Share on other sites

If you're on a mac,

- CMD+Shift+3 will screenshot screen and save it on the desktop

- CMD+Shift+4 will let you select area and save it on desktop (while dragging use Alt and Shift for additonal control of area selection)

+ additionally hold "Ctrl" to have it in clipboard to paste somewhere. (you can even paste it directly into this forum editor)

image.png.28b99e8c2efdea4f3b8cfdb0039973de.png

  • Like 1

Share this post


Link to post
Share on other sites

Thanks for all the suggestions. GreenShot didn't work (captured only closed dropdown,  not the open state). PicPick works great :)

Back to the original question:

Here's what I mean...

If I choose the option shown in single.png, the settings panel never shows up.

If I choose the option shown in multiple.png, everything works as expected.

single.png

multiple.png

  • Like 1

Share this post


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

If I choose the option shown in single.png, the settings panel never shows up.

I can confirm this (PW 3.0.84). Must be a bug. To get around this, like you said previously, just choose the one under Multiple Page Selection (sortable). It will still work with your Single Page field. 

  • Like 2

Share this post


Link to post
Share on other sites

Hi Kongondo,

I have recently installed your latest  Processwire "Blog" module with version 3.0.123 and included your example templates and fields.

Although it is a minor issue, I thought it may help some other Processwire users to know that the "blog_tags" field (of type Page Reference) in the template "blog_post" does not appear to work in our particular hosted environment unless the "Page Auto Complete"  and the "Settings specific to Page Auto Complete" are modified to the first recommended setting as opposed to the second recommended setting (Input field tab) i.e. "Contains phrase or partial word (using fulltext index) - Recommended (this 1st option functions ok).

However, in further testing so far,  I believe that it is a "Core" issue with this particular field type when used in conjunction with the "Page Auto Complete" option as I have been unable to get it working with "Contains phrase or partial word (using LIKE) - Recommended". As this is the default option, it may also be a problem when it is used for other purposes unless you know to change the default afterwards.

Hope this is helpful.

Regards,

Hackasacka

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Robin S
      After forgetting the class name of the wonderful AdminPageFieldEditLinks module for what feels like the 100th time I decided I needed to give my failing memory a helping hand...
      Autocomplete Module Class Name
      Provides class name autocomplete suggestions for the "Add Module From Directory" and "Add Module From URL" fields at Modules > New.
      Requires ProcessWire >= v3.0.16.
      Screencast

      Installation
      Install the Autocomplete Module Class Name module.
      Configuration
      Add Module From Directory
      Choose the type of autocomplete suggestions list: "Module class names from directory" or "Custom list of module class names". The latter could be useful if you regularly install some modules and would prefer a shorter list of autocomplete suggestions. The list of class names in the modules directory is generated when the Autocomplete Module Class Name module is installed. It doesn't update automatically (because the retrieval of the class names is quite slow), but you can use the button underneath when you want to retrieve an updated list of class names from the directory. Add Module From URL
      If you want to see autocomplete suggestions for the "Add Module From URL" field then enter them in the following format:
      [autocomplete suggestion] > [module ZIP url]
      Example: RepeaterImages > https://github.com/Toutouwai/RepeaterImages/archive/master.zip Awesomplete options
      The "fuzzy search" option uses custom filter and item functions for Awesomplete so that the characters you type just have to exist in the autocomplete suggestion item and occur after preceding matches but do not need to be contiguous. Uncheck this option if you prefer the standard Awesomplete matching. Custom settings for Awesomplete can be entered in the "Awesomplete options" field if needed. See the Awesomplete documentation for more information.  
      https://github.com/Toutouwai/AutocompleteModuleClassName
      https://modules.processwire.com/modules/autocomplete-module-class-name/
    • By MilenKo
      Hello all.
      A few days ago I decided to redo my first PW theme (knowledge sharing one) trying to apply some more elegant logic and most important - to learn to filter page results by a Page reference field with some values. So far it is all going well except the fact that I am now at a stage to add some page parameters and am a bit stuck as to how to filter them.
      Here is an example of the structure planned to use:
      !-- Articles (template = articles.php)
      !---- Article 1 (template = articles-inner.php)
      !---- Article 2 ..
      !---- Article 3 ..
      !-- Categories (no template file)
      !---- Category1 (same template as  parent)
      !---- Category2 ..
      !---- Category3 ..
      !-- OS (no template file)
      !---- Windows (same template as parent)
      !---- Linux
      !---- MacOS
      So far the home page and articles-inner pages are fully working. I need to show in the sidebar two blocks; Categories, OS where clicking on one would show only the posts containing the PageReference field value. To list the categories and OS in the block won't be a problem as I would just need to query the parent and list all the children (if any) with the proper markup. However, how to have the Categories and OS blocks link only to the specific posts that is the issue. In my previous version of the knowledge profile, I had the "categories" listed as a parent and the posts matching the category were just children of it. But now my goal is to learn how to add different parameters using Page Reference and have a way to show the results per the specific value.
      How would you organize a similar structure and what approach to take to have a simple and elegant solution?
      Or, if you know of a PW profile that I could dissect and learn the filtering mechanism of Page Reference etc. it would be even better. I am presently looking at the Ghost profile however Wire-approach is still not very much clear to me, unfortunately.
       
    • By rick
      I am not sure how many established ProcessWire users use the Atom IDE, but since it is free, works on linux, and has the features I like, I decided to install it. It is a very nice and comfortable interface. It would be nice to have the advanced.js provider reference the ProcessWire API directly so that users are always up to date.
      There are a vast number of similar IDEs, and I don't suggest that ProcessWire 'endorse' any particular one. However, I do think that having such plugins available for a few can only add to the attraction of ProcessWire.
    • By reed
      Hey y'all! I've been digging through the forums trying to find a workaround for the Page AutoComplete Field. So far, no luck. Here's the problem:
      Currently, to use the Page AutoComplete Field, you have to define a single parent for the pages you want to select from. I want to use the AutoComplete field to add multiple pages from different parents. For instance, I have a field for location, and I want to add the MET Museum and The Louvre, but the MET has parent USA, and the Louvre has parent France. Currently, it's very labor intensive to scroll through a list of 300+ locations, or use AsmSelect to drill down. AutoComplete would be a godsend. 
      I've not been able to find any way to workaround this issue, any ideas? Thanks for any help or recommendations!
      — Reed

       
    • By Qualtext
      Hi community,
      i'am not a pro in module creation and i need someone, who build it better.
      What my stuff at this time does:

      there is a page "Standard". This Page can upload into OR select Images from "Image Library". The pages inside "Image Library" are simple pages with a imageField (single) inside. The page "Standard" looks like this:

      "Select existing Images" ist a pageField. The Inputfield is a AutocompleteField with preview oh the selected pages (from "Image Library"). "Image (add if not exists)" is a imageField (multiple) this two fields togehter and some hooks are the core of my project. select a image form the list, or upload a new one.   The Module has to parts: The new Autocomplete Inputfield for FieldtypePage and a processing for the imagefield via hooks.
      Lets start with the ImageField:
      Upload a Image(s) like everytime in Processwire. After hit "Save": a "Page:saved" hook is checking if the image is already in the Library is checking the basename. if basename already exists, the code compares the two images by pixelanalysis(!) if in Library already: then add the existing Page with this image to the PageField field if not: create a new page with template "Image", add the image there, and add the new page to PageField after all: remove the image from this page (because we linked the image via a page) The pageField is a clone of the existing InputfieldPageAutocomplete, but i extended that with little new function: display images in ___rendeListItem() and the javascript-version after AJAX loading. In my module, you can use as a new label specific string img:{a_image_field.url}:img. 
      This pageField automatically controls the imageField. The selected Parent and Template is the path for new Pages and there Templates.

      I'am testing a lot with this new components. Works fine. I Like this solution for pages where many images are allways the same (like a product-catalog).
      Download the zip and have a look.
      Installation
      Follow this steps:
      Install module "InputfieldPageAutocomplete2" install module "ImageUploadOrSelect" create a Template "Image" now we need a unique name for three fields. For example: "loremipsum". create a field of type image, call it "imageuploadorselect_imagetarget_loremipsum". this field is single image field. no array output! add the field "imageuploadorselect_imagetarget_loremipsum" to template "Image". create a field of type image, call it "imageuploadorselect_imagestemporary_loremipsum". this field is multiple. array output! add this field to a template you decide. For example "basic-page". create a new field of type Page, call it "imageuploadorselect_pages_loremipsum". set up this field like in the image above. Parent: a page you decide (where pages with template "Image" will be created) Template: Image Labelfield: custom Custom page label format: {title} img:{imageuploadorselect_imagetarget_loremipsum.url}:img Inputfieldtype: "PageAutocomplete2". add this field to template from step 8, where the imageField also is. I would be very happy if someone could help.
      How i sad before, i'am not the pro. I looking for somebody who could help me to merge this stuff in one module to share it in the community.
      I commented all the things in the files. There are a lot of detailed information.
      Have nice weekend!
      modules.zip
×
×
  • Create New...