Ability to set the parent of a single

[angrybrad]

Created by: Neal Stammers ([email protected]) on 2015/03/10 18:02:16 +0000
Votes at time of UserVoice import: 5

---

This would allow for creating a fixed structure of 'single' pages.

For example if you had a parent 'about us' page with the following child pages: staff, policies, etc.

Currently the URI has to be hard-coded:

about/staff
about/policies

Which is fine until you need to update the URI for the parent. You would then need to go through each child page and update the URI.

We've tried using structures, but this falls down when you want to use custom templates/fields for lots of individual pages (a staff page is very different from a policies page). You end up with lots of 'Entry types' available, but you probably wouldn't want a user re-using 'staff' or 'policies' template. Hence why a 'single' is perfect.

Having a hierarchy also makes it much easier to render breadcrumbs and side menu's of pages with the same parent.
I'm guessing it would also make it easier to find the single to edit if it's in a tree view

[angrybrad]

Posted by Timothy Kelty ([email protected]) on 2015/04/02 12:33:05 +0000

---

@christian I think putting user group permissions on entry types would be a pretty good workaround. Still not really solving the "singles" issue at hand, but would be an easy way to avoid singles all together.

[angrybrad]

Posted by Neal Stammers ([email protected]) on 2015/03/10 18:02:16 +0000

---

Only one other thing - which is the good thing of singles - is being able to prevent a user being able to change the hierarchy of the entry.

[angrybrad]

Posted by Neal Stammers ([email protected]) on 2015/03/10 18:02:16 +0000

---

@christian - Both those ideas sound great.

I really like structures - We've got it working so that it loads a template based on the 'entry type', field set in the admin area, or a default no matches found. It's brilliant, but we end up with loads of templates available - but your idea of limiting how many times it can be used/hide them would work really well.

[angrybrad]

Posted by Christian ([email protected]) on 2015/03/09 00:49:13 +0000

---

Another, probably not so good idea I just had is if it would make sense to have a limit for each Entry Type? You could set the max. amount of usages of it, before it hides from the dropdowns.

[angrybrad]

Posted by Christian ([email protected]) on 2015/03/09 00:49:13 +0000

---

What do you think about being able to set the Entry Types available for each user group? This would work around of your problem of having single use Entry Types.

Because in my point of view a "Single + Parent in Tree View" is actually a structure section.