[MGNLSITE-85] Publishing default page after vairant caused an error Created: 16/Nov/17  Updated: 16/Nov/17

Status: Open
Project: Magnolia Site Module
Component/s: app
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Critical
Reporter: Jason Wood Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Linux


Attachments: PDF File issue.pdf    
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   

5.5.3

One of our main websites had an issue recently when publishing. The steps...

  • Within the pages app the editor modified a variant
  • The variant happen to be defined on the root site node /uk
  • The editor published the variant page successfully
  • The editor then published the default node with an error (see attached)
  • The entire site content disappeared from public, meaning the users saw an blank page except for a background image (see attached).
  • The editor panicked (60 mins pass)
  • The editor published the default node again and the site was back

The entire site disappearing from public is an issue as we can be in breach given we are an investment company.


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