JModelAdmin and another config option for plugin group???

[Daniel Dimitrov]

Hi @ll,
Currently one can pass a config array to the JModelAdmin that can contain the names of events to call on before and after save...
This is all great, but what about adding another option to set the plugin group?
Currently we do:
JPluginHelper::importPlugin('content');

If we did JPluginHelper::importPlugin(this->plugin_group);
where we set the $this->plugin_group  one would not actually have to override the save method to include his/her own plugin group.

Shall I create a patch for this? Any possible complications from such a feature???

Cheers,
Daniel

[elin]

I think the goal is really to think of all content as content whether it comes from com_content or another content-type extension that is either in the core or from an installed extension. For example all of the core content extensions include the content events.  Overall I think if it is an plugin that relates to working with data that serves as content that it belongs in the content group with a context for the specific extension. So your extension plugin should go into the content group rather than its own group if it is for something like save.  I hope most content type extensions are including the core content events. 

Elin