[BLOSSOM-37] Empty dialog when editing version 0.5 content or using magnolia before 4.3.2 Created: 21/Jan/11  Updated: 06/Dec/14  Resolved: 21/Jan/11

Status: Closed
Project: Blossom
Component/s: None
Affects Version/s: 1.2, 1.2.1
Fix Version/s: 1.2.2

Type: Bug Priority: Major
Reporter: Tobias Mattsson Assignee: Tobias Mattsson
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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   

The removal of BlossomParagraphEditDialog in version 1.2, when anonymous dialogs for paragraphs were changed to be actual real configured and registered dialogs in Magnolia brought about two bugs. The problem for both is that content cannot be edited since the editing dialog shows up empty.

There is a problem with content built using blossom version 0.5. Since it used a different method for connecting content to controllers than is used now.

There is also a problem with versions of magnolia prior to 4.3.2. Before that the paragraph editing dialog did not use the class nodeData set on dialogs.



 Comments   
Comment by Tobias Mattsson [ 10/Feb/11 ]

Introduced a custom ParagraphEditDialog that is backported from 4.4.

Comment by Jan Haderka [ 06/Dec/14 ]

Bulk close of old resolved issues.

Generated at Sun Feb 11 23:29:29 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.