- Issue created by @Kgaut
- Status changed to Fixed
11 days ago 7:45pm 29 April 2025 - πΊπΈUnited States smustgrave
You're right and not sure how they worked before..
- πΊπΈUnited States tregonia
The same issue exists within the
event_log_track_user
module.events_log_track/modules/event_log_track_user/event_log_track_user.module event_log_track_user_insert event_log_track_user_update event_log_track_user_delete
- πΊπΈUnited States nicxvan
It worked because it's a submodule using the same name prefix as the parent module and the submodule bit collides with a real hook.
So when events_log_track is being scanned it finds the function: event_log_track_node_insert as hook_node_insert and it's assigned to event_log_track module. So the system thinks you're implementing this on behalf of the parent module. This gap existed always, but is just more noticeable here.
Once everything is converted to OOP these name collisions cannot happen, but since the appended part of the submodule is a bundle type it can be picked up.
- πΊπΈUnited States tregonia
Updated description to mention that this issue affects multiple entity-based CUD hooks. Additionally, updated the title to "Entity CUD" instead of "Node".
- πΊπΈUnited States nicxvan
Ah and we changed the order we check longest module names first, so now it's getting picked up as hook_insert instead of hook_node_insert. The first hook represents: event_log_track_node and the second hook represents event_log_track.
- πΊπΈUnited States tregonia
Updated each of the entity-type modules to update the hook function names; one commit per module.
- Merge request !76Resolve #3506658 "Entity CUD events are not firing" β (Merged) created by tregonia
- First commit to issue fork.
-
smustgrave β
committed a952d749 on 4.0.x authored by
tregonia β
Resolve #3506658 "Entity CUD events are not firing"
-
smustgrave β
committed a952d749 on 4.0.x authored by
tregonia β