[MAGNOLIA-7026] mgnl:lastModifiedBy is always superuser upon versioning Created: 16/May/17  Updated: 15/Jan/18  Resolved: 19/May/17

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

Type: Bug Priority: Major
Reporter: Oanh Thai Hoang Assignee: Oanh Thai Hoang
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 2d 5h
Original Estimate: 3d

Issue Links:
causality
is causing MAGNOLIA-7242 CopyUtil saves incorrect session Closed
dependency
is depended upon by MGNLACTIVATION-152 mgnl:lastModifiedBy gets reset to ano... Closed
relation
is related to MAGNOLIA-6387 mgnl:lastModifiedBy property is set t... Open
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
Sprint: Saigon 96
Story Points: 5

 Description   

Problem: version creation always have mgnl:lastModifiedBy is superuser since 5.5
To reproduce it:

  • Publish one item
  • Check version of published item
  • Go to JCRUtils to find that version content
  • Observe: lastModifiedBy is always superuser

Source of problem: After I reverted partially code below in CopyUtil (#copyToVersion, #clone and #importNode function). It works well

Using node.save() as different than node.getSession().save(). calling without getSession() won't delegate to WrapperSession so in 5.3 and 5.4 they keep the correct lastModifiedBy


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