No chance for other modules to capture expiring node events
pingers - April 15, 2008 - 01:13
| Project: | Auto Expire |
| Version: | 5.x-1.0 |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | won't fix |
Jump to:
Description
I think this is important for other modules to have the chance to act on expiry events.
I have created the following patch which includes module_invoke_all hooks for 'auto_expire_warn' and 'auto_expire_expire'.
Purging is not so important, because this can already be captured to some degree through nodeapi 'delete'.
Hope this helps.
| Attachment | Size |
|---|---|
| auto_expire.patch | 730 bytes |
#1
Pingers, you posted this patch 1,5 years ago and I apologize that you didn't get a proper reply yet (even though I haven't been involved in this project that long). If you're still listening: Can you provide a use case for these hooks? I think there's nothing wrong with your patch (it's hard to bork a module with those two lines of code :-)) but I'd like to be convinced that it's needed.
#2
Holy blast from the past!
I have no idea what the use case was... only that I wanted to react specifically to a node expiring.
I'm sure this use case could be better implemented through some other means like triggers and actions today...
But thanks for the reply :)
#3
OK, thanks. I'll set this to won't fix for now, but if anyone has a use case for these hooks, please re-open this issue.