> Yes all components that  follow the design pattern of the core components
> use com_config.

> Elin

> On Friday, October 19, 2012 4:06:57 AM UTC-4, nant wrote:

>> So, just to confirm.

>> If any third part component is using Joomla ACL and has and is presents
>> the popup window that allows superamdins to modify allowed permissions for
>> the component based on Joomla ACL groups, then the code that actually
>> handles the Save, Save and Close,  Cancel actions is in the com_config?

>> Or should the third-party component actually fire a trigger in its code
>> somehow?

>> I would think its a Joomla function that is being called by the third
>> party component and Joomla opens-up the pop-up window.

>> I hope you can clarify this.

>> Thanks,
>> Nick

>> On Friday, October 19, 2012 3:00:49 AM UTC+3, elin wrote:

>>> To answer the other question, the global configuration and component
>>> options are set with com_config so it's the job of com_config to do that.
>>> For things like a category or an article it would be the job of the
>>> appropriate component (i.e. com_categories or com_content).

>>> Components are full of triggers of all types.

>>> Elin

>>> On Thursday, October 18, 2012 7:55:47 PM UTC-4, elin wrote:

>>>> I would not have said to put it in the tracker if I thought it wasn't a
>>>> bug.

>>>> There is actually a very old pending issue in the tracker for this
>>>> general situation.

>>>> http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemEd...

>>>> That patch from Ofer does not include com_config but it could.beupdated.

>>>> If you care about issues or have annoyances the way to make them better
>>>> is not to suffer in silence but to help with the work of getting the fixes
>>>> to those problems in.

>>>> It would be fantastic for people to get that tested.

>>>> Elin

>>>> On Thursday, October 18, 2012 8:03:44 AM UTC-4, Youjoomla LLC wrote:

>>>>> I agree with Nick , just the other day I needed onbeforesave in
>>>>> com_templates and is not available.
>>>>> Seems to be available on plugin actions only and on plugin save. It
>>>>> should be in all components onafter/onbefore save.

>>>>> On Thu, Oct 18, 2012 at 3:13 AM, nant <nant...@gmail.com> wrote:

>>>>>> Before I invest more time on this, I need to ask if YOU consider this
>>>>>> a bug or a feature. I do not want to start a never ending tracker
>>>>>> discussion if I open this as a bug and have people (maybe even you)
>>>>>> commenting that it's not a bug but it should be a feature.

>>>>>> Regarding tracker title - i propose:

>>>>>> "com_config not firing any event triggers on Save actions"

>>>>>> Finally, just for clarity - would com_config be responsible for
>>>>>> firing events for other components using the Joomla ACL configuration
>>>>>> methods?

>>>>>> Thanks you Elin for contributing to this.

>>>>>> Nick

>>>>>> On Thursday, October 18, 2012 12:13:43 AM UTC+3, elin wrote:

>>>>>>> Ok so this is probably because of how com_config is working in some
>>>>>>> way differently from the othter edit screens. (A quick look for example
>>>>>>> shows it is extending jControllerLegacy and not JControllerForm). I would
>>>>>>> say that it's totally reasonable to expect that they are going to trigger
>>>>>>> the form events given that you should be able to use a plugin to add or
>>>>>>> replace fields and fieldsets.

>>>>>>> Let's try to dig into what is happening and whether it is something
>>>>>>> that can be fixed in com_config.  Would you go ahead and put it in the
>>>>>>> tracker?

>>>>>>> Elin

>>>>>>> On Wednesday, October 17, 2012 3:52:46 PM UTC-4, nant wrote:

>>>>>>>> I have attached a simple plugin to test the triggers - you need to
>>>>>>>> edit the filename path for your specific root to get it to work.

>>>>>>>> This basically tests all the mentioned triggers and prints a line
>>>>>>>> in the text file if the trigger is fired.

>>>>>>>> Idea is to get something to fire here when a save is done on
>>>>>>>> permissions popup in a Joomla or in a third party component -

>>>>>>>> I tried for example saving the user manager options permissions
>>>>>>>> popup and nothing fires here.

>>>>>>>> Nick

>>>>>>>> On Wednesday, October 17, 2012 6:09:08 PM UTC+3, Brian Shaughnessy
>>>>>>>> wrote:

>>>>>>>>> I see how you've structured your plugin. And I see that when I
>>>>>>>>> save the *plugin* parameters -- the event is triggered.
>>>>>>>>> However -- I don't see how that event is triggered from a
>>>>>>>>> component.

>>>>>>>>> For example --
>>>>>>>>> If I throw a simple echo + exit statement in your plugin at the
>>>>>>>>> top of onExtensionBeforeSave, and edit-save your plugin, I see my debug
>>>>>>>>> text.
>>>>>>>>> Since this is a system plugin, and I've put my debug code before
>>>>>>>>> any context conditions are implemented, one would think that I would get
>>>>>>>>> the text and exit if I then go to any component, view options, and save.
>>>>>>>>> But I don't.

>>>>>>>>> So either the events are not triggered with components, or there
>>>>>>>>> must be some other way to implement the trigger that I am missing.

>>>>>>>>  --
>>>>>> You received this message because you are subscribed to the Google
>>>>>> Groups "Joomla! General Development" group.
>>>>>> To view this discussion on the web, visit
>>>>>> https://groups.google.com/d/msg/joomla-dev-general/-/07u3XNO8eBUJ.

>>>>>> To post to this group, send an email to joomla-de...@googlegroups.com
>>>>>> .
>>>>>> To unsubscribe from this group, send email to
>>>>>> joomla-dev-general+unsubscribe@googlegroups.com.
>>>>>> For more options, visit this group at
>>>>>> http://groups.google.com/group/joomla-dev-general?hl=en-GB.

>>>>> --
>>>>> Best Regards
>>>>> Dan Casky
>>>>> Youjoomla Customer Service
>>>>> +1727-388-6653
>>>>> 5044 17th street N
>>>>> Saint Petersburg ,FL
>>>>> 33714
>>>>> -------------------------------
>>>>> Youjoomla LLC
>>>>> www.youjoomla.com
>>>>> Professional Joomla Web Design Services