Closed (fixed)
Project:
Comment Notify
Version:
6.x-1.4
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
9 Jul 2010 at 18:43 UTC
Updated:
25 Oct 2010 at 01:40 UTC
Jump to comment: Most recent file
Comments
Comment #1
gregglesWhen this happens it seems "normal" priority but "needs more info" until we figure it out.
Comment #2
d4rkngel commentedI'm experimenting this same issue, it happens whenever a user publish a new comment, their preferences get overwritten with "No notifications", I have no idea what could cause this behaviour either.
Sorry for my poor english...
Comment #3
WildBill commentedWhen a logged in user changes the checkbox at the bottom of the comment form, does that modify their default preference? In that case, it would be "by design" I suppose...
Comment #4
greggles@WildBill, yes, the idea is that people who have not yet set a preference should get the checkbox at the bottom of the comment as their preference the first time that they use it.
Comment #5
d4rkngel commentedI didn't notice that he was talking about the comments default preference, yeah I think that is the default behavior, but my problem is with "Receive node follow-up notification e-mails", this is turned off each time a user post a comment and I don't think this is the default behavior since below that option says "You can not disable notifications for individual threads." :\
Comment #6
danylevskyiI think that the solution is here http://drupal.org/node/862730#comment-3344102.
Comment #7
d4rkngel commented@abarmot
I don't know if is the same issue but I'm gonna try it, let see what happens
Comment #8
myha commentedHello, I found a place where this issue can cause (in my case sure). I have installed Profile module and created few categories with fields. When I save my account on some category (not Account) my comment notify settings back to defaults.
Attached patch fix this.
Comment #9
gregglesBrilliant - thanks for the investigation and patch! This makes tons of sense.
Comment #10
gregglesThis issue is not present in 7.x so I committed it to 6.x and it is now fixed http://drupal.org/cvs?commit=434336
Thanks, myha!