mistic100 wrote:

I know that trigger_event returns the var $data but, except that, they are almost identical, so why two functions ?

Well, this is enough. No ? Also note that in the case of an event, the $data might change as it goes through the handlers. In the second case it is going to be the same...

mistic100 wrote:

yeah, but for that we don't need two functions, we can call strtotime without print the result

I don't understand...

mistic100 wrote:

and each time trigger_action is called, no $data is given (that's not a rule but a fact)...

In admin/batch_manager_global.php, you have:

trigger_action('element_set_global_action', $action, $collection);

I added this to trigger actions on batch manager with thumbnails regeneration and websize regeneration...
We don't need trigger_event here, but trigger action...

mistic100 wrote:

Code:

trigger_action('element_set_global_action', $action, $collection);

ok, so what append here if we use trigger_event ?

If you use a trigger_event here, your plugin need to return $action for other plugins.

It's not the same usage... so it's clearer to have two different functions, isn't it?

rvelices wrote:

Also note that in the case of an event, the $data might change as it goes through the handlers. In the second case it is going to be the same...

:-)))

Note that with trigger_action, events are not really "in parallel", events are still loaded with the priority parameter (default 50).