Possible bug in Articles; or is it a Feature Request?

I'm working on a networked blog with the Articles add-on. Because blogs may have sub-blogs, I have to nest Articles Containers within each other. This works sooooooo beautifully. However, in the Resource Tree in the Manager, it does not display the nested Container under the parent Articles Container.

I definitely want to bring it to the author's attention, but I need to know: Is this a bug or a feature request?

If a container is an Articles container it doesn't show its children in the Tree; that was the whole purpose of the custom resource type, to get the load off the Tree.

I would think it would be a feature request to have other containers displayed, just not "leaf" nodes.

Agreed on all points, except one:

Articles Container was designed to take the load off of the Resource Tree, but it only displays children that match the "leaf" template. If a child is added that does not match "leaf", you cannot access it without manually typing the ID (even if it is not a container). This exhibits "bug-type" behavior. If the child is also a container, then you cannot access its children. (Which is kinda beautiful.. LOL) This is true whether you look in the Resource Tree, Articles box, and even the Article itself.

However, it was designed to only have to worry about "leaves". So, this fits within the design consideration, making it a feature request.

The concern here is that it doesn't stop the user from choosing the Articles Container as a parent for any Resource via Resource Settings, Snippet, Plugin or phpMyAdmin. That's why I thought I would ask. I think it is kinda both but wasn't sure how to address it. [ed. note: fuzzicallogic last edited this post 14 years, 1 month ago.]

A possible design solution would be to have it still function the way that it does, except to have non-leaf types display in the Resource tree. Then you would get the best of both, and not have to worry about xPDO creation, changes via the Resource Settings, etc.