[MGNLDATA-40] Magnolia 3.6, Update Issue Created: 28/Jul/08  Updated: 16/Sep/15  Resolved: 29/Jul/08

Status: Closed
Project: Magnolia Data Module (closed)
Component/s: None
Affects Version/s: 1.1.1
Fix Version/s: 1.2.1

Type: Bug Priority: Major
Reporter: Olivier Marti Assignee: Philipp Bärfuss
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File MGNLDATA-40-stacktrace.txt     XML File config.modules.data.config.types.Industry.xml     XML File config.modules.data.dialogs.Industry.xml     XML File config.modules.data.trees.Industry.xml     XML File data.Industries.xml    
Issue Links:
relation
is related to MGNLTOOLS-20 update data module's dataFolder by ad... Closed
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

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.



 Comments   
Comment by Olivier Marti [ 28/Jul/08 ]

Confirmed for different projects, same behaviour.

Comment by Jan Haderka [ 28/Jul/08 ]

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
Comment by Olivier Marti [ 28/Jul/08 ]

Full Error in attachment.

Comment by Olivier Marti [ 28/Jul/08 ]

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

Comment by Olivier Marti [ 28/Jul/08 ]

Tree configuration added as well.

Comment by Philipp Bracher [ 28/Jul/08 ]

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

Comment by Philipp Bracher [ 28/Jul/08 ]

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).

Comment by Michael Mühlebach [ 16/Sep/15 ]

This ticket was closed because former resolved tickets are deemed to be closed now. If this assumption is untrue in this particular case please feel free to reopen the ticket again.

Generated at Mon Feb 12 05:10:45 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.