[MGNLUI-2445] Internal Error and nodes in weird state on public instance after deactivation or deletion Created: 21/Nov/13  Updated: 09/Mar/21  Resolved: 09/Mar/21

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Critical
Reporter: Milan Divilek Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MGNLUI-2231 Publishing the deletion of a page lea... 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   

When having app open in public instance with selected node. Then deactivate or delete the structure which contains selected node on author instance. This lead to "Internal error" and crashes whole admincentral on public instance and after refresh the admincentral deactivated/deleted content is still visible(in weird state).

How to reproduce:
1. On public instance select "article" page (/demo-project/about/subsection-articles/article)
2. On author instance deactivate "about" page (if workflow is used then approve it)
3. Go back to public instance and try collapse the "about" page
4. It leads to "Internal error. Please notify the administrator. Take note of any unsaved data, and click here to continue."
5. After refreshing the admincentral by clicking on "click here". The deactivated pages are still presented in tree, but they are missing their icons and are moved to the top level


Generated at Mon Feb 12 08:56:41 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.