Stop page becoming a container

Hi all,

If I create a resource under a resource the parent becomes a container however I don’t want this to happen, is there any setting that can be changed to stop parents becoming a container as I can’t seem to fine one.

Using revo 2.7

Thanks

I don’t think if this exist.

I think this would make a great feature request.

For what purpose?

Quote from: OpenGeek at Jan 16, 2011, 01:53 PM

I think this would make a great feature request.

Thanks Jason, Done http://bugs.modx.com/issues/3508

Sorry Jason, I’ve added that as a bug but can’t edit that area, could you correct it to improvement please

Quote from: sottwell at Jan 16, 2011, 02:00 PM

For what purpose?

As has been discussed before, to prevent the automatic changing of parent Resources to containers when adding children, since being a container is separate from the state of having children in Revo. If you have containers set to have different URL suffixes, this can break all links to the existing parent Resource just by adding children, which IMO, is very bad.

Quote from: sottwell at Jan 16, 2011, 02:00 PM

For what purpose?

For my purpose it’s because of friendly URL’s, if I create a document called new1 under new, the friendly URL would be site.com/new/new1.html which I don’t want to happen, I just want it to be site.com/new1.html as it starts breaking links to images etc

Ah, so sometimes you want friendly alias paths and sometimes you don’t. What effect would this have on the building of the Resource Tree? In Evo, if you "turn off" a resource’s is_parent setting, its children disappear from the Tree (or at least it used to; maybe this got fixed?).

I just have to go back and edit the parent every time I add a new page and take the tick out of container, the tree stays the same it just removes the second element of the friendly URL.

Wouldn’t be a problem on a none live site but as I’m still adding campsites to my site I have to do it after every one added.

Maybe an auto_parent system setting would be the way to go.

In any event, it seems that the resource/create processor should only set the parent’s container status on the birth of the first child. If there’s already a sibling and it’s not set to container, the user must not want it to be a container.

http://bugs.modx.com/issues/3509