When there is more than one vocabulary and a user subscribes to two tags from those vocabularies and a node has those two tags, the notification is sent out twice by mail.

Please do only send out one notification per user and nodeid.

Comments

salvis’s picture

salvis
he/his
commented

subscribing

Leeteq’s picture

Leeteq commented

subscribing

Anonymous’s picture

Anonymous (not verified) commented

subscribing

Dabitch’s picture

Dabitch commented

subscribing

icstars’s picture

icstars commented

subscribing

icstars’s picture

icstars commented

upon looking into this further, it does not appear to be a bug in the module per se.

our duplicates are sent when there are 100s of people getting notified at once. it appears that our cron job is timing out, leaving the record in subscription_holding in place, and resending to everyone on the next cron run.

this is unfortunate, as our hosting provider limits emails per hour to 400 in the terms of service. without an ability to throttle how many messages go out at once, we have a broken system and a violation of our tos. i wish user_send was implemented as a throttled queue instead of a live send.

Anonymous’s picture

Anonymous (not verified) commented

It is definitely a problem even for those of us who have their own servers. I am not so much concerned with server load as with user overload as it is really annoying to get the same email 10 times when you happen to be subscribe to several taxonomy tags - once should be enough and would reduce server load too. It seems to me, icstars, that your problem is different from the problem described by kus - we want only one email sent per subscription to a node, no matter how many of your subscription criteria that node fits, you want some sort of throttle mechanism - maybe opening a new bug / feature request may be better

Dabitch’s picture

Dabitch commented

Confirming that the cron job times out on own server with no mail limitations.

bdragon’s picture

bdragon commented
Status: Active » Closed (fixed)

5.x-2.0 is a complete rewrite, therefore any bugs in it are new. All prior releases will be obsolete when 5.x-2.0 final is out. Closing references to bugs in prior releases for this reason. Please help test 5.x-2.0 betas. Thank you!