The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.For modules that want to be notified when a user has subscribed to something. Failing that, a trigger.
Obviously not a major concern, though ;)
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | subscriptions.admin_.inc_.patch | 948 bytes | gengel |
| #2 | subscriptions.module.patch | 3.42 KB | gengel |
| #2 | subscriptions_content.module.patch | 1.13 KB | gengel |
| #2 | subscriptions_taxonomy.module.patch | 715 bytes | gengel |
| #2 | subscriptions_ui.module.patch | 784 bytes | gengel |
Comments
Comment #1
salvisYes, please supply a patch.
Comment #2
gengel commentedOkay!
Mostly, this just adds a module_invoke_all before writing to the database. The one major change was adding a subscription_delete_subscription and replacing manual SQL DELETEs with calls to this, so that all subscription deletes may also invoke the hook.
Comment #3
gengel commentedComment #4
gengel commentedWhat are the odds of this patch being accepted?
Comment #5
salvisI'll get back to you this weekend, promise.
(Having a single unified patch rather than five separate ones would certainly make the reviewers life easier...)
Comment #6
salvisYes, now that I think about it, it's much less work for you to create a unified patch than it is for me to apply five separate patches. So please do that (and take the current -dev, of course).
Comment #7
salvis