One problem with this is that other applications stick stuff in there as well, which causes it to show up at the bottom of the /etp page -- the page that lets you edit your home page. But these items have no title, so it looks kindof silly, and obviously the 'edit' links don't work.
Right now, the non-ETP-related contents are:
- a file-storage root folder
- two user portraits
- two bug-tracker root folders
It just seems wrong that my site's root pages are intermixed with various application folders.
What's the right fix here:
a) other packages should stop using the -100 root folder -- what should they do instead?
b) ETP should create its own "site root" folder, under which other folders would get created.
c) ETP should just find a way to filder out which items belongs to itself, and ignore the rest.
d) something else ...
In keeping with the posting I just made over at
I'm thinking why we need folders for this anyway. I mean, we at least want one CR folder hierarchy, which exactly mimics the site map, so why not just use package_id?
Then *maybe* we *also* want to be able to have CR folders for subdividing things within a package instance.
E.g. a CR folder per forum in a forums package -- even though I think packages should only have a single forum per instance, and we should use acs-subsite/ETP/Portals to give you the list of available forums and let you create new ones.
What would other examples be, where you'd want CR folders that weren't mapped to the site-map? Maybe none.