alkahest

Okay, I can confirm this now - and it looks like it's excluding them properly regardless of access permissions. What was confusing me is that I was selecting a parent that was too high up. So for example, if I say parent!=1057, it excludes the bolded parents below (who are children of Menus - 1057), but not the grandchildren: - Menus (id 1057) -- A Custom Menu --- Arbitrary Link (uses a "menu" template) --- Arbitrary Link --- Page in Hierarchy -- A Custom Menu --- Arbitrary Link --- Arbitrary Link --- Page in Hierarchy So it seems like the only question that remains is, is it possible to exclude a whole tree?

Ooh, my bad - that's good news. Okay, let me get myself on the same branch and test it out.

I definitely agree on those admin pages. Though it seems to ignore excluding the parent, whether or not you're a superuser. As for the custom list select thing, I don't think it's a question of access permissions - like, if I'm specifying just a set of pages to display in a list, I don't see how it should matter what role I am. For example, in the cheat sheet, it looks like you can specify role and access permissions as methods, so unless you specify those in conjunction with excluding pages from the selector's results, it shouldn't matter if I'm a superuser or a client role, don't you think?

Ah I see, you can assign permissions at the template level - that fixes the editing problem for the "client" role. RE what they can pick: They can pick anything that's not a menu (not anything under "Menus"). I've come to the same conclusion you have too - if you're a superuser, it shows everything regardless of what you've excluded as a selector. My client role, however, sees what's been limited by the selector (it doesn't show admin pages like you said), except that it's ignoring the parent!=1057, which should exclude children of the Menus page (I assume). However, if we're specifying a selector that says "don't include these pages in the list" shouldn't it exclude them for the superuser as well? That seems like a bug.

Okay, so I tried creating a role called "client" and gave it all permissions except for "Administer users," then I created a user "client" using that role. Interestingly the client can't do anything except view pages. The pages like 404 and search though are hidden for this user. Next I tried using the custom selector like you recommended above... My setup is: HOME - Page - Page - Page - Menus (id 1057) -- A Custom Menu --- Arbitrary Link (uses a "menu" template) --- Arbitrary Link --- Page in Hierarchy -- A Custom Menu ... Menu templates have a field that lets them pick a Page or enter a URL. The Page field (ideally) would be populated with only valid pages in the hierarchy, so under Input I deselected "Parent" and "Template" and I set the Input field type to "Select". Then tried using a selector under "Custom Selector": template!=admin, parent!=1057 (where 1057 is the Menus page, because they shouldn't be able to pick a Menu) However the resulting Select dropdown is a list of everything, including admin pages. So I'm not sure what I'm doing wrong here... (Ultimately I created a field on the homepage that lets them pick a child of the Menus tree, so they can basically choose a menu to go into a "Primary Menu Slot" - in a way this imitates how WordPress allows you to pick menus to go into template-defined slots.)

Ahh, I see - I'm going to try using the custom selector when I get to work on Monday. Sounds like that's exactly what I need, then I'll report back. Thank you two for the tips.

Your first suggestion (to use Access control) seems to be on the right track: If I log in as any other role than superuser, the hidden pages are hidden. The only problem I see now is that even if I make a new role (say "Client") and assign her every permission except for the ability to edit templates and do admin things, she still can't edit pages? I must be missing something, because Guest and the new "client" role can only view pages. I've also tried giving Guest more permissions but it makes no difference. To clarify: I do want the client to be able to edit/see the "Menu" page and menu item children (I don't have it set as hidden - sorry in my comment above I included it as one of the ones I intend to hide, but I'm not actually), just not other hidden pages like say "404" and "API" if those pages exist and were marked as hidden. So it looks like this would work, if only any other role besides superuser could edit pages.

Yeah, I imagine a scenario where the client is adding new items as menu items in the tree, but things like "Search" and "Menus" and even the 404 page (or any other pages that are children of Home but not actually in the site's hierarchy) would appear as options when they shouldn't be.

Having difficulty finding this question previously asked, but here goes: I'm following Macrura's tutorial for creating custom menus (where the menus aren't a reflection of the site's page hierarchy). As a first step, I've created a page called Menus with children that use a template with a Pages field type. This is set to use PageListSelect as the input type, which lets me pick a specific page in the hierarchy from any parent tree. Is it possible to exclude certain pages from being selectable in the tree? It notes that I can't use PageListSelect and restrict by page template, so how else might I go about it? These pages are already set to be "Hidden: Excluded from lists and searches" so I'm not sure why they still appear in the list of selectable pages?

Thanks!

I've tried searching the forum in case this was already asked, so sorry if I'm duplicating questions here: I want to pick a page from a dropdown so I can associate it with a content type. I created a "Page" type field, but it populates only top-level parents in the dropdown. How would you go about listing all pages and their children instead?