[MAGNOLIA-293] deleting a parent node should warn there are children Created: 11/Feb/05 Updated: 17/Mar/09 Resolved: 17/May/06 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | admininterface |
| Affects Version/s: | 2.0 Final |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor |
| Reporter: | Chris Stephens | Assignee: | Philipp Bärfuss |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
all |
||
| 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 an admin user elects to delete a node that has children, this fact should be emphasised strongly to the user in the JavaScript popup - especially in the absence of an undelete or rollback capability. [I see this as having perhaps more importance right now - in the absence of any role-based ability to prevent authors from deleting pages: if they can edit a level in the hierarchy they can delete nodes there also. I believe another Jira issue deals with this latter issue.] |
| Comments |
| Comment by Philipp Bracher [ 17/May/06 ] |
|
we warn in general in the case of deletion. |