Show unlisted pages in link field

The link field (and the link mark in the writer field) seems to show only pages whose status is “listed” in the page select. Is there a way to show unlisted pages, too? I couldn’t find any documentation about that (or I’m just blind which is more likely :grin:).

Should show unlisted pages (i.e. all published pages) as well, do you mean drafts maybe?

Home and news and sandbox in the screenshot are unlisted pages.

Currently, you cannot limit or modify the page list in the picker. And linking to drafts which are not publicly accessible is probably not recommendable.

OK, this is a different problem, it seems. So, the thing is that I have standard pages and then I have a product listing under a “products” page that has a template that isn’t existing, so to speak, i. e. the product listing parent page isn’t shown in the page tree. This is the blueprint for site.yml:

sections:
  seiten:
    type: pages
    label: Standardseiten
    status: all
    create:
      - default
    image:
      cover: true
  produkte:
    type: pages
    label: Produktseiten
    status: all
    templates:
      - produkt
    image:
      cover: true
    parent: site.find('produkte')

The link field only shows the default pages but not the product sub-pages. I need those to be selectable, too, somehow.

Sorry for the bump but I guess after three days of silence this is justified. :slight_smile:
Do you need any other info or clarification? Or is this simply a case of “I don’t know either”?

Sorry, yes, but what does the dialog then actually look like? As you can see above, the default dialog is the complete page tree with no option to remove any pages.

What I don’t understand is how the two sections shown above come into play here or what this means:

I mean, those pages do exist in the content folder?

This is what the page tree looks like in the link field/node:

The actual content file structure looks something like this:

content/
├─ site.txt
├─ _drafts/
├─ 1_vorteile/
│  ├─ aktionen.txt
├─ 2_impressum/
│  ├─ default.txt
├─ 3_startseite/
│  ├─ startseite.txt
├─ faq/
│  ├─ faq.txt
├─ fehler/
│  ├─ fehler.txt
├─ nutzungsbedingungen/
│  ├─ default.txt
├─ produkte/
│  ├─ produkte.txt
│  ├─ 1_produkt1/
│  │  ├─ produkt.txt
│  ├─ 2_produkt2/
│  │  ├─ produkt.txt
│  ├─ etc…/

The produkte.txt is an empty template. That whole folder has been created for the sole purpose of holding the product sub pages.

Hm, is there anything specia about this page, does it have a model of some sort.

I mean, it’s completely irrelevant if that page has a template or not. If I add a folder salad with some children cucumber, tomatoes, onions, with just the text files, no blueprints, no template, no model, no controller, they will show up there:

So please test this with a random page and double check, you have no custom code somewhere that might prevent the page from showing up there.

Thanks for pointing me in the right direction. There is indeed a blueprint for the template that looks like this:

title: Produktübersicht
options:
  #access: false
  list: false
  changeSlug: false
  changeStatus: false
  duplicate: false
  delete: false
  preview: false
  update: false
  move: false

sections:
  produkte:
    type: pages
    template: produkt

The culprit is the list: false line. Commenting this out will show the page in the page list in the link field but it will also show it in the panel, which I don’t want. How can I avoid that?

If it shows up in a Pages section, you can filter it out:

Thanks. I find it hard to understand the possible filtering options. This page doesn’t have a template (it falls back to the default), there is only the folder and the content file called produkte.txt. By which property can I filter then?

It does have a content file, so that is an “intendedTemplate” (filterBy('intendedTemplate', '!=', 'produkte'))in Kirby and you can filter by that. Or simply exclude the file by name.

Or you list the templates allowed in a section via the templates option, without using the query option. Whatever seems more appropriate.

Thank you very much, this works. :slight_smile: