When subscriptions is enabled with storylink of voting up/down module, and when a user subscribes for notifications on the storylink node, an email is sent each time a user votes up or down on that module.
This should be activated only for comments and not for every vote.
Not sure if this should be posted here or in subscriptions module. I've posted it in both places.
Comments
Comment #1
drupalzack commentedHeard back from the Subscriptions folk. http://drupal.org/node/83016
As I understand, subscriptions module reacts to triggers from the storylink module. Should storylink send out triggers for every vote? Shouldn't it be only for node updates (like content update) and comment update?
Other than that, the module works just great! One of the most powerful modules in drupal IMO.
Thanks!
Comment #2
drupalzack commentedMore testing:
If I vote on a comment, it doesn't send an email. Which is what is expected.
But when I vote on a node, it sends out an email. An email for every vote.
Comment #3
frjo commentedIs it only when you vote on nodes of type storylink or does it happen when you vote on e.g. a blog post also?
Comment #4
drupalzack commentedI tried the same on a 'page'. When I update the contents of a page, I receive a email as I should. When I up or down vote, I do not receive an email. Works as it should.
Looks like this is an issue only with storylink.
Comment #5
drupalzack commentedI think this is related:
I have views tracker turned on which shows the most recent nodes.
For a page, if I up/down vote, the tracker doesn't show 'updated' (as it should)
But when I do the same for storylink, the tracker shows 'updated' (only the vote has changed, not contents hence the tracker should not be showing 'updated').
For some reason storylink is sending out an 'update' trigger for every vote up or down. It should do that only for content changes.
Comment #6
drupalzack commentedWorks fine with weblinks too (similar to storylinks but comes with the links package). Doesn't send out an email for every vote
Comment #7
drupalzack commentedI did a fresh installation and this problem is not there. Please ignore this bug. Truly sorry. Must've been something in my configuration.
Closing this as it is a non issue.