[MAGNOLIA-3332] Delete versioned content on deletion of main content Created: 22/Oct/10 Updated: 28/Jul/11 Resolved: 22/Jul/11 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | 4.3.7 |
| Fix Version/s: | 4.4.5 |
| Type: | Bug | Priority: | Critical |
| 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)
|
||||||||||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||||||||||
| Date of First Response: | |||||||||||||
| Description |
|
When content is deleted, it's versioned counterpart from mgnlVersion is not deleted so the versions of such content are not purged. Ideally we delete mgnlVersion copy of content together with the original or in the least we should run the cleanup job on the instance to purge such content periodically. |
| Comments |
| Comment by Danilo Ghirardelli [ 07/Jul/11 ] |
|
Is this internal cleaning of nodes or this means that there will be no way to see deleted content even accessing to the parent node? One of the best feature of versioning should be to retrieve or see (accidentally) deleted nodes... |
| Comment by Jan Haderka [ 07/Jul/11 ] |
|
Staged deletion of the content is already implemented and nothing is going to change on this. |
| Comment by Danilo Ghirardelli [ 07/Jul/11 ] |
|
Well... You know the average user... Confirm messages are never really read, and you understand that something is missing only when it's in public production... And unfortunately there is no separate "DELETE" permission that you can deny to the average user. |
| Comment by Jan Haderka [ 07/Jul/11 ] |
|
By that logic you should never ever delete or throw away anything |
| Comment by Jan Haderka [ 22/Jul/11 ] |
|
Done for both 4.4 branch and trunk. The test for direct deletion on JCR API in trunk will fail until SCRUM-310 can be fixed. |