[MGNLDEMO-347] Stories page has a broken version history Created: 09/Oct/20  Updated: 18/Jan/21  Resolved: 09/Oct/20

Status: Closed
Project: Magnolia Demo Projects
Component/s: magnolia-travels
Affects Version/s: 1.5
Fix Version/s: None

Type: Bug Priority: Trivial
Reporter: Richard Gange Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File broken-version-history.png    
Issue Links:
relation
is related to MGNLSYNC-42 Synchronization manager does not comp... Closed
is related to MGNLDEMO-332 Stories page has invalid embedded Jav... Closed
is related to MGNLUI-6301 showVersionAction should notify about... 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

 Description   

Reproduce

  • Open the Pages app
  • Click the page /travel/stories
  • From the actionbar, click show versions.
  • Observe there are no versions available in the drop down.

This ticket is to document an example of a broken version history. Ideally the bootstrap file that imports the page should be fixed. On the other hand it's beneficial for testing reasons to have such a page.

If you run a synchronization against the travel demo you will get the following warning:

2020-09-30 18:12:13,487 ERROR ia.synchronization.commands.SynchronizationCommand: 
Broken version history. No versions found for node /travel/stories.

2020-09-30 18:12:13,697 ERROR ia.synchronization.commands.SynchronizationCommand: 
Broken version history. No versions found for node /travel/stories/story.

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