I definitely agree with you on this! My suggestion exactly serves this concept.
...I like being able to have a Resource with children treated as if it’s not a folder.
Sorry, but I see that Revo rc1 does just the opposite -- it automatically changes the ’isfolder’ attribute of a resource when you create a child document to it.
I absolutely separate the concepts of having children and being a container/folder Resource. i.e. when you add or remove files from file system folders, you don’t automatically change the folder to a file.
For me, it’s not a question if it’s a good habit the system asks the user to confirm a change on a resource different than that is actually being created or deleted, so the user wouldn’t notice it otherwise.
Personally, I don’t want it asking me anything or auto-adjusting the isfolder attribute unless I tell it to specifically.
I’m actually making a menu that relates on the container status.
What is the significance of container status then?
I installed Google site-map snippet quite a few betas ago, and Google does not seem to mind the changes much. Running analytics and watching the reports, as well as webmaster tools, and other resources we have -- has shown no issues with switching from a bbb.html to a bbb/.
The issue appears to come in when the names and/or locations completely change.
Well that would be a bug then.
Quote from: OpenGeek at Mar 24, 2010, 05:37 PMSorry, but I see that Revo rc1 does just the opposite -- it automatically changes the ’isfolder’ attribute of a resource when you create a child document to it.
I absolutely separate the concepts of having children and being a container/folder Resource. i.e. when you add or remove files from file system folders, you don’t automatically change the folder to a file.
I can accept this only if modx asks me to confirm to change that attribute on the FIRST child resource being saved, and if it was like that, why not ask me if I want to change that attribute back when the LAST child being deleted? THIS would really prevent modx from "automatically change the folder to a file" or the file to a folder!
Yes, in Revo, the plus sign indicating children should be separate from the icon indicating it is a container.
If a resource has children, but is not flagged as being a container, will the children show in the Resource Tree? They won’t in Revo.
Correct, this is a change in behavior from Evo.
Just checked in Evo 1.0.2; it won’t let the Container flag be cleared if there are children.
There must be another bug then.
Yes, in Revo, the plus sign indicating children should be separate from the icon indicating it is a container.

No, I just spoke inaccurately, having children drives the icon and expansion link; regardless, having children and being a container are separated.
Quote from: OpenGeek at Mar 25, 2010, 11:35 AMThere must be another bug then.
Yes, in Revo, the plus sign indicating children should be separate from the icon indicating it is a container.
In Revo rc1 the icon changes only when there are children.