[EE4] after_channel_field_update and after_channel_field_save hooks/events not firing when adding or updating a channel field

Confirmed, will be fixed in next build!

Sweet, thanks!

The events are firing, but I think there is a mixup.

When creating a new field after_channel_field_save is called. When editing an existing field after_channel_field_save and after_channel_field_update is called. I don’t believe this was a case in EE3.

I assume it should be:

after_channel_field_save = new after_channel_field_update = edit/update existing

That should be correct, actually. The Save hook is meant to fire on all modifications, whether new or existing, then if you need to get granular, use Insert or Update. I’m not aware of this changing from EE3 as I’m pretty sure that’s always how it was meant to work. So, to summarize:

New entity: after_insert and after_save

Existing entity: after_update and after_save

You’re right. Maybe I was using them incorrectly in EE3 but never really noticed. Thanks for the clarification.

Doesn’t look like after_channel_field_delete is firing though :(

Sorry to inundate you with these.

Yes I can reproduce. Question though: do you know if that hook even worked in EE3? I’m not sure how it would have, looking at things.

Yep, because Publisher is using it. If a field is removed I need to also remove it from the publisher table to keep things clean.

Ahh ok I see what’s happening. It’s due to a performance optimization, which is the same commit that caused no hooks to work in the first place. Will try to find a way around it.

I think we’ll just do this for now: open system/ee/EllisLab/ExpressionEngine/Service/Model/Model.php and add this to the bottom of the initialize() method:

if ($this->getMetaData('hook_id'))
{
    $this->forwardEventToHooks('delete');
};