How would you recommend handling situations where multiple modules define on_change behavior for the same field in the same form?
Let's say we have a module dependency structure like this, and each module has their own on_change() method for the same field:
Module A (in core)
--Module B (a community extension)
--Module C (some additional own customization)
When the on_change of Module C gets triggered, what's the best way to make sure that also A and B's on_change methods get called with their correct parameters? Is it possible to somehow define multiple on_change methods for a single field or are you supposed to call the superclass methods similarly as in create(), write() etc. methods?
Please try to give a substantial answer. If you wanted to comment on the question or answer, just use the commenting tool. Please remember that you can always revise your answers - no need to answer the same question twice. Also, please don't forget to vote - it really helps to select the best questions and answers!
About This Community
|Asked: 11/6/13, 12:48 PM|
|Seen: 1618 times|
|Last updated: 12/4/15, 3:26 PM|