[MAGNOLIA-5776] MgnlPropertySetting wrapper fails after move or copy followed by update in same session Created: 20/May/14  Updated: 27/May/14  Resolved: 23/May/14

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: 5.2.5

Type: Bug Priority: Neutral
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:
causality
is causing MAGNOLIA-5789 Restoring deleted nodes does not upda... Closed
is causing MGNLDAM-399 Error on duplicating asset Closed
relation
is related to MGNLRSSAGG-173 Scheduled import job fails on update ... Closed
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 performing move or copy followed by property update in same session, wrapper gets stale copies of nodes between system session and regular user session and is not able to perform save of modifications from both, without reseting (refresh w/ keepChanges=false) one first and re-applying changes.



 Comments   
Comment by Philip Mundt [ 22/May/14 ]

Reopened due to problems with markNodeAsDeleted command. Status of pages "marked as deleted" is not updated to "modified" anymore.

Comment by Jan Haderka [ 23/May/14 ]

Fix on MAGNOLIA-5776 branch.

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