Anon commenters don't receive notification of anon replies
juniperphoenix - October 24, 2009 - 16:17
| Project: | Comment Notify |
| Version: | 7.x-1.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Description
My site recently enabled Comment Notify subscriptions for anonymous users. (We've been using it successfully with authenticated users for a while now.) When an anonymous user leaves a comment and subscribes to replies, he receives notifications of replies to his comment made by registered users. However, if a reply is made by another anonymous user, no notification is sent.
#1
Can you try with the latest 6.x-1.x-dev and see if this is fixed or if it's worse?
#2
I just upgraded to 6.x-1.x-dev and tested again. There was no change.
#3
i'm having the same problem, both with v1.2 and 6.x-1.x-dev.
does it work at all for anybody else?
#4
I have an idea what could be the problem:
Comment Notify doesnt notify users of their own comments, right? Therefore, anonymous user "Guest" won't be notified about comments by another "Guest".
Is there a way to disable that feature, e.g. with a patch? I wouldn't know how to do it and would appreciate any help.
#5
@axel_exa - actually the way that the module keeps track of who it has alerted is by e-mail so your theory is not the cause of this bug. (you can see this in the $sent_to variable). Any other ideas?
Right now there are no simpletests that cover this case and I'd like to add them so we have the tests to prove that it is working but for tonight it is dinner time ;)
#6
I've now committed a test which shows that this does work as designed, so I'm marking this fixed.
There are probably some specific settings you could have which this test doesn't cover, so if you have some more details on how to reproduce the problem let me know. I've also done a bit of work on the 6.x-1.x-dev so maybe the problem you saw has been fixed in another issue recently and upgrading will fix it.
#7
Thanks for working on this. I just tried the patch, and then the latest 6.x-1.x-dev, and the problem is persisting. Any suggestions about what other settings I might need to check?
#8
The only thing I can say is to start with a blank site and try re-reading the README.txt and configure everything and see if it works or not. If not, post the steps you followed and I can try repeating them. If it does work, keep configuring to make it the same as your current config and we can see what the step that breaks it is.
#9
Automatically closed -- issue fixed for 2 weeks with no activity.