[MGNLDIFF-45] first change on a page is not shown by diff module Created: 02/Sep/13  Updated: 19/May/22  Resolved: 19/May/22

Status: Closed
Project: Magnolia Diff Module
Component/s: None
Affects Version/s: 1.3
Fix Version/s: Backlog

Type: Bug Priority: Neutral
Reporter: Boris Kraft Assignee: Unassigned
Resolution: Won't Do 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   

the first time I change a page, launch a workflow, and then try to view the changes, no changes are shown. SInce I did change the page, there should be something that DIFF is able to show me.



 Comments   
Comment by Philip Mundt [ 01/Oct/13 ]

Not sure how we should solve this, as:

  • the workflow will create the first version of that page, thus
  • the first version equals the current non-versioned state of the page and
  • there is no version before the first version.
Comment by Jan Haderka [ 01/Oct/13 ]

I don't think this is really an issue. What is confusing here is that you see and edit the page you did NOT create. It was bootstrapped and you know it exists on public leading to assumption it should have been versioned. However, if you have had created the page itself ALL content of the page is NEW. You are effectively comparing it to the blank page.

What we could do to prevent this confusion is to make sure that all bootstrapped content of demo project is actually versioned upon installation.

Comment by Roman Kovařík [ 19/May/22 ]

Hello,

This ticket is now marked as closed due to one of the following reasons:

  • A long period of inactivity
  • Uses an old or Beta version of an application, module, or framework that we no longer support
  • The issue is no longer reproducible or has been fixed in later versions

If you are still facing a problem or consider this issue still relevant, please feel free to re-open the ticket and we will reach out to you.

Thank you,
The Magnolia Team

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