[EEPUBLISH-42] Page path (name) isn't rolled back after failed publication Created: 23/Feb/22  Updated: 20/Jul/22  Resolved: 05/Apr/22

Status: Closed
Project: Publishing Transactional
Component/s: None
Affects Version/s: 1.2.1
Fix Version/s: 1.2.2

Type: Bug Priority: Medium
Reporter: Marek Lesiak Assignee: Jaromir Sarf
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[X]* Steps to reproduce, expected, and actual results filled
[X]* Affected version filled
Date of First Response:
Epic Link: Nucleus Quality Maintenance
Sprint: Nucleus 6, Nucleus 7
Story Points: 3
Team: Nucleus

 Description   

Steps to reproduce

  1. Configure 2 public receivers;
  2. Create page in root of page app;
  3. Publish page; (page must be published to all public instances);
  4. Change page name; Change any content on page(or title);
  5. Re-publish page; With fail on second(or not first) configured receiver;
  6. After fail, content(or title) will be rollback(on first receiver ,where was success published page), but name will be not rollback, which provide different content(page addresses) on public instances;

Expected results

Expected that after fail publication action, content must be left same on all public instances;

Actual results

Different page addresses(on public instances) after fail publication on not first receivers;

Workaround

Development notes



 Comments   
Comment by Roman Kovařík [ 01/Mar/22 ]

Discovery completed:

JcrRollbackOperation restores the node content, but not the node name explicitly.

Generated at Mon Feb 12 10:38:10 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.