[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: |
|
||||||||
| Issue Links: |
|
||||||||
| 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. 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 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:
no exceptions at all. Could you attach following files:
|
| 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 |
| Comment by Philipp Bracher [ 28/Jul/08 ] |
|
OK the problem is that 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. |