[MAGNOLIA-2907] System ignores class data field when creating custom dialog Created: 22/Oct/09  Updated: 23/Jan/13  Resolved: 21/May/10

Status: Closed
Project: Magnolia
Component/s: admininterface
Affects Version/s: 4.1.1
Fix Version/s: 4.3.2

Type: Bug Priority: Major
Reporter: Valery Visich Assignee: Philipp Bärfuss
Resolution: Fixed Votes: 0
Labels: Custom, Dialog, Subclassing
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows vista x86


Attachments: PNG File CustomDialog.png     PNG File EditParagraph.png    
Issue Links:
relation
is related to MAGNOLIA-2878 Dialog class and saveHandler is no mo... 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   

Steps to reproduce:
1. Create new Paragraph "jobsParagraph " within Magnolia Module Samples;
2. Define Custom Dialog "jobsEditDialog" for this paragraph;
3. In the source code of Magnolia Module Samples SNAPSHOT 4.2 add new class JobsEditDialog inherited from ParagraphEditDialog to be able to override the method ParagraphEditDialog.onPreSave. Re-build new Magnolia Module Samples SNAPSHOT 4.2 and install it in Magnolia.
4. Configure this new custom dialog "jobsEditDialog" to use newly created class JobsEditDialog instead of ParagraphEditDialog - set the class datanode JobsEditDialog.

Result:
System ignores class datanode here, It uses modules/adminInterface/dialogs/editParagraph/class or selectParagraph/class instead when creating or editing new paragraph.
However system uses all other information from samples/modules/dialogs/jobsEditDialog when constructs the custom dialog.

See screenshots.



 Comments   
Comment by Philipp Bärfuss [ 21/May/10 ]

This problem was introduce by MAGNOLIA-2370. All paragraphs are using a single dialog mvc handler which is configured in the templating module: editParagraph. This dialog uses the ParagraphEditDialog handler class.

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