Allow parent-child relationship and ordering for Non-Menu Pages
My Wildapricot Membership Backend is getting MESSY! I am not able to organize "Non-Menu" items to have "children"
Is there something in the works where I can create a page and then create SUBPAGES that are Not Menu Items?
When I click on Reorder my Pages, it only allows this functionality for Menu Items.
I would like this feature too.
We have webpages which are "not in the menu" but they are actually in use! Ex: the JOIN form.
We also have a plethora of "demo pages" which are nice to keep around (for future website inspiration) but I wish I could stick them into one "folder" instead of wading through 20 demo pages to find the 2 -3 important pages that are actually in use on the site (but are not displayed in the main Menu).
it also makes it harder for me to train/teach people to use the site. They get boggled by the many many webpages ...
[Deleted User] commented
As an aside to "simulate" hierarchy for pages not in menu I propose to customers that the page be prefixed with a numbering scheme.
1, 2, 3 for the top level and
1a, 1b for pages under 1
2a, 2b, 2c for pages under 2
1. Old main page
1a. Old sub page under Old main page
[Deleted User] commented
One more thing to add here, that is somewhat related. Moving a set of menus at the same time into "not in menu" would be helpful. Especially moving 1 menu with a bunch of submenu items all at once into not in menu. Combined with being able to sort and create hierarchy in the not in menu section this would make it easier to organize "draft" pages.
I think there are several sets of page types also and maybe what WA needs to look at is why people put stuff in menus and why they put stuff "not in menus"
1. Menus that are public or restricted are there obviously to be part of the master navigation
2. Not in menu items have various "statuses"
a. Pages that are actually "draft" pages not ready to be in the menu and are in a staging sort of state
b. Pages that are "admin"-only and rather than placing them in menu they are taken out of the menu to reduce confusion in the admin back end and the "public view"
c. Pages that are public or restricted and are actually meant to be linked to from a secondary navigation or from just a page but are not meant to be part of the menu system.
d. Pages that USED to be in a menu and are now "archived" for future use, these are most likely "admin" restricted but sometimes people forget to set this setting so they really should NOT be accessible by the public, archiving a page should set its state into admin only.
The use cases for putting pages into a menu and otherwise are varied.
WordPress for example deals with this quite differently - they separate the idea of content and menus and allow the creation of multiple menus that can be placed as widgets throughout the site. Basically every menu in WordPress is a secondary menu with potential hierarchy and design. I tend to like that approach better because it gives you more flexibility to create multiple menus. The current "secondary navigation" gadget attempts to simulate this but it doesn't support hierarchy and therefore is used only to show navigation for a part of the site.
I also want to see both features suggested by Angel (https://forums.wildapricot.com/users/86860621-angel).
So for the "Pages Not Under Menu", I want to "Reorder Pages".
Furthermore, I want to be able to virtually group those pages together so that the virtual group can be "closed" or "opened" to reduce left-bar clutter, e.g. with disclosure triangles as used in file list views for Mac, Windows, and other GUI platforms.
Finally, I want these virtual groups to be able to contain both pages and additional virtual groups.
Margaret Timberlake commented
Yes! Yes! Yes! We have many pages that we don't want in the menu and have trouble finding anything because there is on way to sort them or categorize them.
Dana Robb commented
On the sample, you can see how it would be good to move "events" out of the list of job pages.
Dana Robb commented
I would like to be able to set the order for the website pages that don't appear in the menu. Some organizations have a large number of them, and it would be helpful to be able to group them together in logical ways.
Mel Whaley commented
Ability to sort/move/organize site "pages not in menu" similar to the way we can currently sort pages that are "Menu Pages"
Evgeny Zaritovskiy commented
Current behavior was made on purpose: we thought that "order" only make sense of menu pages. Other pages do not require ordering or structuring (parent-child relation). It looks like we were wrong.
Anyways, you can use a workaround for now: create "Admin-only" root page (in menun) and place all pages you want as children, make then as "in menu". This will effectively hide the whole section from user's menu, but will be shown for admins.
Becky Parsons commented
I agree. Please give us the ability to have "child" pages for non-menu pages. After being on WA for several years, our "non-menu" page list is getting large and it's not organized well.
In version 5 we can easily manage pages that are listed in a menu.
However, I have many pages that are accessed through a link from a menu page but the linked page is not in the menu. This allows me to keep the menu area fairly clean but still provides access to the linked pages.
You provide a section in Page Management called "Not in Menu" which seems to be the obvious place to save these pages. However when we select the Reorder Pages option, the Not in Menu section is specifically excluded which means that all these linked pages are in random order that cannot be managed.
The page management issue would be much easier if we could leave the linked pages which are not to appear in the menu in the same hierarchy as the menu pages they belong to.
To do this, I'd suggest that you::
1. Rename the current "Not in Menu" section to "Page Archive", and
2. Provide a way to allow any pages that are in the Menu area to be flagged as "Do not Include in Menu".
This would allow us to place pages that are not currently in use but may be revived in the future in the Page Archive. It would also allow us to keep the active linked pages logically associated with their parent.