[MAGNOLIA-2866] Ordering issue with copied/renamed nodes Created: 15/Sep/09  Updated: 04/Dec/13  Resolved: 04/Dec/13

Status: Closed
Project: Magnolia
Component/s: activation
Affects Version/s: 4.1, 4.0.2, 3.6.7, 3.6.8, 4.0.3
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Magnolia International Assignee: Unassigned
Resolution: Cannot Reproduce 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
Date of First Response:

 Description   
  1. copy a test page (previously activated)
  2. rename the original to test-old
  3. rename the copy to test (the former name)
  4. activate the parent of both

The resulting order on the public instance(s) is wrong.



 Comments   
Comment by Zdenek Skodik [ 15/Sep/09 ]

doesn't occur since Magnolia 4.0.1

Comment by Magnolia International [ 15/Sep/09 ]

hmm i was just able to reproduce this with 4.0.3

Comment by Zdenek Skodik [ 16/Sep/09 ]

well I supposed that once the bug is fixed it doesn't occurs at later versions.
I was also able to reproduce it also with 4.0.2 and 4.1 (until the original renamed page is reactivated).

Comment by Jan Haderka [ 04/Dec/13 ]

This issue is not reproducible in Magnolia 5.2.

Generated at Mon Feb 12 03:40:52 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.