Gregory

Of course, if you guys would integrate this "fix" into Magnolia things would look differently. But in order to do it the Magnolia way, it would be helpful, if you would tell me what you would preferre:

- I could change HierarchicalUserManager to use something else than ItemType.FOLDER -> nt:folder
        - e.g. mgnl:content
- or introduce mgnl:folder which could be a custom nodetype extending nt:folder => I would have to adapt UsersTreeConfiguration too in order to have it display the new folder type. - Or I could even change ItemTyp to have it return a "mgnl:folder" item type when asked for ItemType.FOLDER => This _might_ have some influence on something I do not know about, but would be the best way IMHO.

What do you think?

Cheers,
Will

On 15.08.2008, at 11:59, Grégory Joseph wrote:

I'm faced with the problem that HierarchicalUserManager uses nt:folder to structure the user accounts - and nt:folder nodes do not have a UUID anymore (since Mag 3.6). Due to the lack of UUID the nodes cannot be activated anymore. To resolve the problem Grégory proposed:
On 09.08.2008, at 15:06, Will Scheidegger wrote:

"Either fix HUM to use another type or let it had mix:referenceable at runtime."

I'd rather not change HUM because I want my solution to be as much "Magnolia-compatible" (for future updates) as possible.

Well, fixing includes not only modifying your local copy but also provide patches for possible inclusion in the codebase.


More info, more questions: I tried adding the mixin "mix:referencable" to the nodes of the type nt:folder. Unfortunately they do not seem to be "open" for it:

ERROR info.magnolia.cms.core.DefaultContent DefaultContent.java(addMixin:914) 15.08.2008 11:37:48 Node - / public/a/at does not allow mixin type - mix:referenceable

Then you'll need to change the nt definitions anyway.

And I don't know much about nodetype manipulation, and nothing about nodetype manipulation at runtime. Can anyone give me a few pointers to get started?

I found Content.addMixin():
- Is that what I want? Isn't it rather a super type "mix:referencable" that should be assigned to my nodes (as I do it with custom nodetypes)?

the "mix:" prefix indicates that it IS a mixin, indeed.


----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------


----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------

Reply via email to