Strike back: It's not me creating mgnl:contentNode, but the magnolia dialog controls (all dialogs which handle multiple values) ;-P And that's o.k... It really does not make any sense creating a second set of controls just for the data module which do the same thing as the original controls but use dataItemNode instead of mgnl:contentNode.
On top of it, I'm not so sure if adding mgnl:contentNode to the tree configuration will do the trick. The mgnl:contentNodes are clearly displayed in the data JCR browser but are still not activated... The node types a tree can display should not have any influence on the "Activate with subnodes..." command. It does not have one in the website tree for sure. There, mgnl:contentNodes are not displayed, but still they are activated. I think the problem must lay somewhere in the activation command itself. When I find the time, I'll have a look at it if nobody else has already located the problem. -will On 25.03.2010, at 14:45, Jan Haderka wrote: > > Strike back: Why do you create subitems of mgnl:contentNode in your custom > data type? :D > > What you see is actually expected behavior. From the very beginning of the > Data Module, it supports item type "dataItem" for the main type (and all > custom types have this as a supertype) and "dataItemNode" for the child > nodes. This is similar to mgnl:content/mgnl:contentNode system used in the > website. > Now of course you might want to have some special sub item type (and indeed > you have them for example when using hierarchical types). As long as such > child items have dataItemNode as their supertype you don't need to do > anything. If they are hierarchical subtyped you have defined, again you don't > need to do anything since Magnolia will take care of the configuration for > you. The only problem is when you bring in extra type programatically such as > in your case. Then you need to change the _tree_ configuration to include > such a type in the "itemTypes" property of the tree. See > config:/modules/data/trees/company/itemTypes for example. Company type has 5 > subtypes and those need to be listed there along with the basic > (dataItemNode) type. > > HTH, > Jan > > > > From: Will Scheidegger [mailto:[email protected]] > To: Magnolia User-List [mailto:[email protected]] > Sent: Thu, 25 Mar 2010 10:22:35 +0100 > Subject: [magnolia-user] "Activate with subnodes..." in the data module > > > Dear Magnolians > > I'm tripping over something that might be related to [MGNLDATA-97]. When I > try to activate a whole data node structure (by selecting "Activate with > subnodes..." on a dataFolder node) I do get all dataFolder nodes and all > dataItem sub-type nodes activated (and of course the mgnl:nodeDatas), but no > mgnl:contentNodes (used for instance on stuff like checkbox lists and so on). > When I then select a single dataItem sub-type (i.e. one of the data nodes in > the tree) and choose "Activate with subnodes..." it gets activated with the > mgnl:contentNodes types. > > Now before I add a new issue to the JIRA: Has anyone seen similar > (mis)behavior? > > Cheers, > -will > > > [MGNLDATA-97] = http://jira.magnolia-cms.com/browse/MGNLDATA-97 > > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- > ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
