Update mechanism improvements
(MAGNOLIA-5529)
|
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | modulemechanism, updatemechanism |
| Affects Version/s: | 3.5 |
| Fix Version/s: | None |
| Type: | Sub-task | Priority: | Major |
| Reporter: | Magnolia International | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
Currently, only modules found through a module descriptor are loaded/initialized. We should provide some level of support for user modules who merely want to group their configuration (dialogs, paragraphs, templates, ...) under a single node. See |
| Comments |
| Comment by Magnolia International [ 16/Jun/08 ] |
|
related: any module should be observed such that adding a paragraphs or other observed nodes will register this new node with the relevant ObservedManager. -> see |
| 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. |