For modules that want to be notified when a user has subscribed to something. Failing that, a trigger.

Obviously not a major concern, though ;)

CommentFileSizeAuthor
#2 subscriptions.admin_.inc_.patch948 bytesgengel
#2 subscriptions.module.patch3.42 KBgengel
#2 subscriptions_content.module.patch1.13 KBgengel
#2 subscriptions_taxonomy.module.patch715 bytesgengel
#2 subscriptions_ui.module.patch784 bytesgengel

Comments

salvis’s picture

salvis
he/his
commented

Yes, please supply a patch.

gengel’s picture

gengel commented
StatusFileSize
new subscriptions_ui.module.patch784 bytes
new subscriptions_taxonomy.module.patch715 bytes
new subscriptions_content.module.patch1.13 KB
new subscriptions.module.patch3.42 KB
new subscriptions.admin_.inc_.patch948 bytes

Okay!

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.

gengel’s picture

gengel commented
Status: Active » Needs review
gengel’s picture

gengel commented

What are the odds of this patch being accepted?

salvis’s picture

salvis
he/his
commented

I'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...)

salvis’s picture

salvis
he/his
commented
Status: Needs review » Needs work

Yes, 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).

salvis’s picture

salvis
he/his
commented
Issue summary: View changes
Status: Needs work » Closed (outdated)