[MAGNOLIA-3470] Allow direct deletion of content when there are no subscribers defined on the instance Created: 17/Dec/10 Updated: 08/Sep/13 Resolved: 10/Jan/11 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | admininterface |
| Affects Version/s: | 4.4.1 |
| Fix Version/s: | 4.4.2, 4.5 |
| Type: | Improvement | Priority: | Major |
| Reporter: | Jan Haderka | Assignee: | Jan Haderka |
| 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)
|
||||||||||||||||
| Date of First Response: | |||||||||||||||||
| Description |
|
When running on instance without any subscribers, we should allow direct deletion of the content. This is the situation that occurs usually in two cases - developer instance or public instance. In either case the deletion should be immediate to simplify and speed up the process. |
| Comments |
| Comment by Will Scheidegger [ 19/Nov/12 ] |
|
I think this issue should be reopened. On my unmolested 4.5.6 Mag CE with no active subscribers I still cannot delete a dms node directly. |
| Comment by Jan Haderka [ 20/Nov/12 ] |
|
If anything then please create new issue (pbly in DMS project) and link it to this one. However this is what I just tried on demoauthor and what worked just fine:
HTH, |