Hm... I thought about this too, because I imported the config from the old installation instead of creating it with the UI. So as last test before I posted this question I removed the config (/modules/data/ config/types/mynode, /modules/data/trees/mynode), all data and recreated it using the GUI... but also the same name. Do you think that this might be the problem? Where are the node type definitions being stored? And how would I add mix:referencable to it?

Thanks for the help!

-will

On 23.06.2008, at 17:10, Jan Haderka wrote:

Hi Will,
is that from a data type you defined yourself manually or via DataModule
UI? If it is the former, then you need to make sure that you add
mix:referencable to it, if the latter it is most likely a bug.
Cheers,
Jan

On Mon, 2008-06-23 at 17:03 +0200, Will Scheidegger wrote:
I'm testing Magnolia 3.6 M1 with a site which uses the data module.
I'm pretty happy with the speed, but I'm facing a show stopper now.
The following code works fine on Magnolia 3.5.4 but throws an
exception in 3.6m1

The code:

             Content itemValues = (Content) matching.next();
             String itemValuesUUID = itemValues.getUUID();

The exception:

javax.jcr.UnsupportedRepositoryOperationException
at org.apache.jackrabbit.core.NodeImpl.getUUID(NodeImpl.java: 2830)
     at
info.magnolia.cms.core.DefaultContent.getUUID(DefaultContent.java: 897)

Additional info: The "itemValues" node which is causing the above is a
data module node so it has its own nodetype.

Any ideas anyone? Thanks!

Regards,
Will

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


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


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

Reply via email to