[MAGNOLIA-4362] Missing node type definition for mgnl:deleted in custom_nodetypes.xml which is created after modules installation Created: 30/Mar/12 Updated: 02/Sep/13 Resolved: 17/Apr/12 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.5.3 |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Roman Milos | Assignee: | Robert Šiška |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| 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)
|
||||||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
If the file with custom node types definitions (custom_nodetypes.xml) is missing and modules are already installed then during startup of application is created new file, in which one node definition (mgnl:deleted) is missing. Other definition are same as in the file which is created during installation of modules. Then Magnolia is unable mark node as deleted without definition of "mgnl:deleted". |
| Comments |
| Comment by Robert Šiška [ 05/Apr/12 ] |
|
It happens because "mgnl:deleted" is registered from magnolia-module-admininterface (setup.for4_4), while the rest of mgnl nodetypes is bootstrapped from magnolia-core. Is there a reason for mgnl:deleted not to be defined with the rest of the nodetypes in core bootstrap file? |