[
http://jira.magnolia-cms.com/browse/BLOSSOM-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tobias Mattsson updated BLOSSOM-37:
-----------------------------------
Summary: Empty dialog when editing version 0.5 content or using
magnolia before 4.3.2 (was: Incompatibility with version 0.5 content)
Priority: Major (was: Neutral)
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.
was: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 a bug with content built using version 0.5.
The problem is that this content cannot be edited, adding new content and
rendering the existing content works. The dialog for editing is empty.
Introduced a custom ParagraphEditDialog that is backported from 4.4.
> Empty dialog when editing version 0.5 content or using magnolia before 4.3.2
> ----------------------------------------------------------------------------
>
> Key: BLOSSOM-37
> URL: http://jira.magnolia-cms.com/browse/BLOSSOM-37
> Project: Magnolia Blossom Module
> Issue Type: Bug
> Affects Versions: 1.2, 1.2.1
> Reporter: Tobias Mattsson
> Assignee: Tobias Mattsson
> Priority: Major
> Fix For: 1.2.2
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
