[MGNLPN-403] Editing a Blossom Component Through its Dialog Causes ClassCastException Created: 09/Oct/17  Updated: 30/Sep/21  Resolved: 30/Sep/21

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

Type: Bug Priority: Neutral
Reporter: Julian Nodarse Assignee: Unassigned
Resolution: Obsolete Votes: 1
Labels: y2k
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Reported on Magnolia 5.4.13 using magnolia-personalization-components-1.3.4


Issue Links:
Relates
relates to MGNLPN-373 Pages App: when editing 2 pages simul... 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
Date of First Response:

 Description   

There was a commit in code where the line

final FormDialogPresenter formDialogPresenter = dialogPresenterFactory.createFormDialogPresenter(dialogId);

Got changed to

 final ElementAwareFormDialogPresenter formDialogPresenter = (ElementAwareFormDialogPresenter) dialogPresenterFactory.createFormDialogPresenter(dialogId);

(Line 104 of magnolia-personalization-components/src/main/java/info/magnolia/personalization/ui/pages/action/EditVariantAction.java)

The addition of the attempt to cast ElementAwareFormDialogPresenter to the FormDialogPresenter is causing a ClassCastException when a user tries to open a Blossom component’s dialog as indicated here : SUPPORT-7991

Some extra info:
The commit for this code is 0d07d0e7be9 which is part of the fixes for MGNLPN-373



 Comments   
Comment by Frank Sommer [ 02/Nov/17 ]

see BLOSSOM-243 and MGNLPN-332

Comment by Marta Kobus [ 30/Sep/21 ]

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 06:37:18 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.