Dear Magnolians
I'm trying to find a work around for the limitations of hierarchically defined
node types. If you have the following node types
- organization
- staff
- person
you cannot have
- university
- staff
- person
You _can_ have it in the JCR node type definitions, but you cannot define the
types like this in the data module because it will try to define "staff" and
"person" twice and will block it (yes, copying the definitions in the config
tree from organization to university does not work either).
-> IMO it would be better if the data module would define the node types in a
flat list and would allow to build the hierarchy separately.
But how would you solve the problem above on a short term? My need is to
"extend" the organization node with additional attributes. I don't even need a
separate node type. The two could be in totally different trees. How can I
configure a tree to behave like a organization tree (allowing me to create
organizations with staff lists) but display a different dialog for the
organizations with additional input elements? The dialogs are selected by the
node types. Is there some other way to tell the tree what dialog to use for my
node of the type organization?
Thanks!
-will
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
