[MAGNOLIA-1364] custom node types and namespaces Created: 09/Feb/07  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 3.1 M1
Fix Version/s: None

Type: Improvement Priority: Major
Reporter: Oliver Lietz Assignee: Sameer Charles
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

Sub-Tasks:
Key
Summary
Type
Status
Assignee
MAGNOLIA-1365 node handling by Tree class Sub-task Closed Sameer Charles  
MAGNOLIA-1377 Content#addMixin(String type) Sub-task Closed  
MAGNOLIA-1506 ids and names used for HTML elements ... Sub-task Closed Oliver Lietz  
MAGNOLIA-1620 Button/ButtonSet: don't rely on _SETB... Sub-task Closed Oliver Lietz  
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:

 Description   

enables Magnolia to handle custom node types and namespaces

This issue is related to MAGNOLIA-1346 and MAGNOLIA-1348, but it looks like that there is far more to do to get this fully supported.



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