What is the use of container resource, and the use of resource's parent? Are they relevant to each other?
A container will act as a container, as a folder does on your server.
A container, as a folder, need not contain anything.
The name folder is not dependent on containing children.
In the case of MODx, a container has a special attribute, and mere appearance of folder, namely it has no file extension
Because itself is a file, it is not a folder, but has the mere appearance. It ends in a forward slash
A parent has the relative name of parent because it has kids. No children, no title of parent!
The title parent depends on the existence of children.
A parent has a file extension unless you specify otherwise, that is, you make it a container.
A parent is not a folder, since itself is a file.
www.test.com/container/
can be without children
will become a parent when it has children
it will have no file extension even when it becomes a parent
www.test.com/parent.html
must have children
can be made a container
it will lose its extension when it becomes a container (www.test.com/parent/)
Somebody please correct any mistakes here
TinymceWrapper: Complete back/frontend content solution.
Harden your MODX site by
passwording your three main folders:
core, manager, connectors and renaming your
assets (thank me later!)
5 ways to sniff / hack your own sites; even with renamed/hidden folders, burst them all up, to see how secure you are not.
Parent and container are completely independent. They are definitely not relevant to each other. The 'parent' field holds the ID of the resource's parent resource (or 0 if it's at the top level of the tree). The parent field is mainly to organize the resources in the tree and in Wayfinder menus.
The container checkbox sets the 'isfolder' field of the resource. The behavior of that field has changed. It used to stick, but now, as donshakepeare ssys, it will change to checked automatically when the resource gets children, so there's no real point in setting it yourself, imo. It will affect the URL depending on the container_suffix System Setting (default is /), but you can change it to match the regular suffix is you want all pages to have the same suffix. (e.g., html).
Technically, a container resource is just a regular resource with the isfolder field set to 1. It can look like any of your other pages with the same template and can have TVs, content, summary, etc..
