[MAGNOLIA-7036] Versions are removed too eagerly when calling node.remove() or session.removeItem() Created: 18/May/17  Updated: 18/May/17

Status: Open
Project: Magnolia
Component/s: None
Affects Version/s: 5.3, 5.4, 5.5
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Jaroslav Simak Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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

 Description   

Calling node.remove() (and most likely also session.removeItem(absPath)) will result into versions being removed before node is actually removed by calling node.getSession().save().

Versions should be removed once node.save() (node.getSession().save()) are called.


Generated at Mon Feb 12 04:20:08 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.