[MGNLUI-2999] ArrayIndexOutOfBoundsException when working with tree after deleting a page variant Created: 13/Jun/14  Updated: 20/Jun/14  Resolved: 13/Jun/14

Status: Closed
Project: Magnolia UI
Component/s: pages app, tree/list
Affects Version/s: 5.3
Fix Version/s: 5.3

Type: Bug Priority: Blocker
Reporter: Andreas Weder Assignee: Aleksandr Pchelintcev
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

eebundle snapshot: magnolia-enterprise-bundle-5.3-20140612.210538-295


Attachments: PNG File 1 Deleted variants node.png     PNG File 2 Publish deletion successful.png     PNG File 3 Internal error when working w tree.png     PNG File 4 Exception in the logs.png    
Issue Links:
Cloners
clones MGNLUI-2966 Exception when working with the page ... Closed
Relates
relates to MGNLUI-3024 ArrayIndexOutOfBoundsException when w... Closed
supersession
is superseded by MGNLUI-3001 Tree/View gets out of sync if worked ... Open
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
Release notes required:
Yes

 Description   

The problem and exception in the linked issue is still visible in the latest snapshot release.

Steps to reproduce:

  • open the Pages app and delete the Variants node using "Delete all variants"
  • publish the change using "Publish deletion" on the Variants node
  • to get the internal error and exception, attempt to e.g. close and open the master page of the variant you just deleted.
  • the system only fully recovers, when you close and re-open Pages


 Comments   
Comment by Andreas Weder [ 13/Jun/14 ]

The case described here is fixed in the latest snapshot release magnolia-enterprise-bundle-5.3-20140613.102607-296, which tracks location changes to detect some cases where it has to refresh itself.

However, the problem still exists for asynchrously running actions that do not cause such a location change, or if multiple session are involved. I've thus created and linked a follow-up issue for this.

Generated at Mon Feb 12 09:02:13 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.