[MGNLFORUM-94] Cleanup nodetypes, provide update tasks / tools Created: 24/Jul/09  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Forum (closed)
Component/s: None
Affects Version/s: None
Fix Version/s: Ideas

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

Issue Links:
dependency
is depended upon by MGNLCMNT-14 Rename "reference" to "referencingPag... Closed
is depended upon by MGNLCMNT-15 User info properties don't need to be... Closed
relation
is related to MGNLFORUM-92 Moderation list query is broken since... Closed
is related to MGNLFORUM-127 Add metaData nodes to forum and threa... Closed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
MGNLFORUM-122 Allow arbitrary extra properties in n... Sub-task Closed Magnolia International  
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:

 Description   
  1. MGNLCMNT-14 (referencing pages)
  2. MGNLCMNT-15 (user info properties)
  3. remove mgnl:messageProperties
  4. let all forum nodetypes have arbitrary properties
  5. use prefixes for known/system properties if possible (probably a problem with the current gui)

+ provide update tasks and migration tool(s) for everything since 1.0
(there's already some code in magnolia-tools, and a condition in the forum module, which might or might become irrelevant)



 Comments   
Comment by Fabrizio Giustina [ 16/Aug/10 ]

done "4. let all forum nodetypes have arbitrary properties".
Implementing re-registering the existing nodetypes, so the task depends on jackrabbit (tested with version 1.6 and 2.1).

The removal of mgnl:messageProperties (2) can't be done in the same way since mgnl:messageProperties is a childd node of mgnl:message and jackrabbit doesn't support the removal of childNodeDefinitions. THis unfortunately would require a manual editing of the nodetype definition file

Comment by Fabrizio Giustina [ 16/Aug/10 ]

ressigning to gregory, not sure what to do about MGNLCMNT-* and task 5.

Comment by Christoph Meier [ 09/Dec/13 ]

Moved from fix to version 4.0 to Ideas.

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:39 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.