[MAGNOLIA-4793] Define the behavior of MarkNodeAsDeletedCommand when versioning is unavailable Created: 24/Jan/13  Updated: 01/Jul/15  Resolved: 26/Jan/15

Status: Closed
Project: Magnolia
Component/s: activation, core
Affects Version/s: None
Fix Version/s: 5.3.7

Type: Task Priority: Major
Reporter: Jozef Chocholacek Assignee: Federico Grilli
Resolution: Fixed Votes: 0
Labels: support
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Release notes required:
Yes
Date of First Response:

 Description   

The preDeleteNode method code starts with a line:

// TODO: versioning might be "unsupported" do we still purge in such case?

There is a need to decide the proper behaviour, implement it into code, and document it.



 Comments   
Comment by Richard Unger [ 27/Nov/14 ]

We are affected by this problem in production. Please take a look at this bug.

Comment by Federico Grilli [ 26/Jan/15 ]

For the release notes/documentation:
the chosen behaviour here is to not version if versioning isn't available

Generated at Mon Feb 12 03:59:05 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.