Cleanup nodetypes, provide update tasks / tools (MGNLFORUM-94)

[MGNLFORUM-122] Allow arbitrary extra properties in nodetypes Created: 30/Nov/10  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Forum (closed)
Component/s: None
Affects Version/s: None
Fix Version/s: 1.3.x

Type: Sub-task Priority: Major
Reporter: Magnolia International Assignee: Magnolia International
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Date of First Response:

 Comments   
Comment by Jan Haderka [ 04/Jul/11 ]

To finish work on this issue we need:

  • update task to check that the correct node type definitions are in place
    • in case NTs are not updated, and user is running on JCR 2.0, task should execute ReRegisterNodeTypes task to update definition.
    • in case NTs are not updated, and user is running on JCR 1.0, task will point user to documentation page describing necessary changes and stop the installation
  • document necessary NT changes and how to make them (similar to the documentation for NT change between Magnolia 3.5 and 3.6)
  • write script for magnolia-tools that can be used by EE users to execute NT update automatically even on JCR 1.0 repositories
Comment by Magnolia International [ 04/Jul/11 ]

The difference in NTs is the addition of

<propertyDefinition name="*" multiple="false" ...
<propertyDefinition name="*" multiple="true" ...

on mgnl:forum, mgnl:thread and mgnl:message

Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 02:00:55 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.