SaveHandler is ignored for subtypes.
------------------------------------
Key: MGNLDATA-126
URL: http://jira.magnolia-cms.com/browse/MGNLDATA-126
Project: Magnolia Data Module
Issue Type: Bug
Affects Versions: 1.6.3
Reporter: Danilo Ghirardelli
Assignee: Philipp Bärfuss
Each type or subtype has its own dialog definition. If you customize the
saveHandler for a type, everything is working correctly, but if you customize
the saveHandler for a subtype, the definition is ignored and only the parent
type saveHandler is used.
Steps to reproduce:
- create a new type x, with a subtype y.
- in the dialog definition, customize the saveHandler for x with a class (Save1
extends DataSaveHandler)
- in the dialog definition, customize the saveHandler for y with a different
class (Save2 extends DataSaveHandler)
- create a x object using the admin interface, and the called saveHandler is
Save1 (which is correct)
- create a y object under x using the admin interface, the dialog displayed is
the right one for the y type, but when you save, the saveHandler called is the
x one (Save1) and not the y one (Save2)
I would expect that the saveHandler used when saving y is Save2, not Save1 of x.
The fastest workaround (which I'm using now) is to define a single savehandler
for both, and simply check the saving node type to get the right behaviour
depending on the type. Not the best but at least works.
--
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/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
