[#MGNLDATA-40] Magnolia 3.6, Update Issue

Magnolia Data Module

Magnolia 3.6, Update Issue

Created: 28/Jul/08 10:21 AM Updated: 17/Mar/09 07:40 PM

Component/s:

None

Affects Version/s:

1.1.1

Fix Version/s:

1.2.1

Time Tracking:

Not Specified

File Attachments:

config.modules.data.config.types.Industry.xml (2 kB)
2.

config.modules.data.dialogs.Industry.xml (5 kB)
3.

config.modules.data.trees.Industry.xml (2 kB)
4.

data.Industries.xml (26 kB)
5.

MGNLDATA-40-stacktrace.txt (14 kB)

Issue Links:

relation

This issue is related to:

~~MGNLTOOLS-20~~ update data module's dataFolder by adding mandatory child node MetaData

Labels:
Resolution Date:	29/Jul/08 10:42 AM
Date of First Response:	28/Jul/08 11:19 AM

Description

« Hide

When updateing magnolia 3.5.8 to version 3.6 you are not longer able to store data withing data-module anymore as the mandatory child node {}MetaData for the topnodes (datatype) not seem to exsist.
The following error occours:

19:12:56,328 INFO [STDOUT] ERROR info.magnolia.cms.core.DefaultHierarchyManager DefaultHierarchyManager.java(save:561) 25.07.2008 19:12:56 /Text-Modules: mandatory child node {}MetaData does not exist
javax.jcr.nodetype.ConstraintViolationException: /Text-Modules: mandatory child node {}MetaData does not exist
at org.apache.jackrabbit.core.ItemImpl.validateTransientItems(ItemImpl.java:550)
at org.apache.jackrabbit.core.ItemImpl.save(ItemImpl.java:1205)
at org.apache.jackrabbit.core.SessionImpl.save(SessionImpl.java:897)
at info.magnolia.cms.core.DefaultHierarchyManager.save(DefaultHierarchyManager.java:558)
at info.magnolia.module.admininterface.SaveHandlerImpl.save(SaveHandlerImpl.java:241)
at info.magnolia.module.admininterface.DialogMVCHandler.onSave(DialogMVCHandler.java:315)

Not reproduce able with plain new 3.6 installation.

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Olivier Marti added a comment - 28/Jul/08 10:30 AM

Confirmed for different projects, same behaviour.

[ Permlink | « Hide ]

Jan Haderka added a comment - 28/Jul/08 11:19 AM

I just failed to reproduce this issue on following setup:

clean 3.5.8 installation
created custom node type
created some data
upgraded to 3.6
updated previously created data
created more new data

no exceptions at all.

Could you attach following files:

log file with whole stacktrace
export of data that can't be modified anymore
custom_nodetypes.xml from your repository

[ Permlink | « Hide ]

Olivier Marti added a comment - 28/Jul/08 01:57 PM - edited

Full Error in attachment.

[ Permlink | « Hide ]

Olivier Marti added a comment - 28/Jul/08 01:59 PM

Export of data and bootstrap-file of its dialog and type added.

[ Permlink | « Hide ]

Olivier Marti added a comment - 28/Jul/08 03:42 PM

Tree configuration added as well.

[ Permlink | « Hide ]

Philipp Bracher [old account - now Philipp Bärfuss] added a comment - 28/Jul/08 05:11 PM

The issue appears if one updates from magnolia 3.5.4 (data 1.1) to 3.5.8 (data 1.1.1) to 3.6 (data 1.2).

So it looks as if the update task for ~~MGNLDATA-25~~ is not executed in the update

[ Permlink | « Hide ]

Philipp Bracher [old account - now Philipp Bärfuss] added a comment - 28/Jul/08 05:23 PM

OK the problem is that ~~MGNLDATA-25~~ has been originally fixed for 1.1.1 but has been postponed for 1.2. But the version handler still registers the task for 1.1.1 and is therefore never executed.

I had also a look at info.magnolia.tools.setup.for_36.UpdateNodeTypesDefinition.java which is very much questionable and should be part of the node type update tool (adding meta data as a mandatory auto created child).

Scheduled Maintenance: over the next few days, we will update Jira to a newer version.

Magnolia 3.6, Update Issue