[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: |
|
||||
| Template: |
|
||||
| Acceptance criteria: |
Empty
|
||||
| Task DoR: |
Empty
|
||||
| Release notes required: |
Yes
|
||||
| Date of First Response: | |||||
| Description |
|
The preDeleteNode method code starts with a line:
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: |