Closed (fixed)
Project:
Comment Notify
Version:
6.x-1.2
Component:
Miscellaneous
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
9 Jun 2009 at 20:08 UTC
Updated:
2 Sep 2009 at 10:35 UTC
Jump to comment: Most recent file
Comments
Comment #1
gregglesCan you try the latest development release?
Comment #2
gregglesIn a second round of testing the item you mentioned works fine...but I found a new bug.
Comment #3
gregglesAnd fixed - http://drupal.org/cvs?commit=225074
Comment #5
elijah lynnI just installed the latest dev release and it still is not obeying the settings I specify in admin/settings/comment_notify.
Comment #6
elijah lynnOk, it was working. Our developer figured out that it was remembering the user settings. So I created a new user and it defaulted to the setting I specified.
Comment #7
Rhino commentedThis seems to only work on new users.
Is there any way I can set all previously registered users to have default notification _on_ witch a quick kick straight in mysql?
Comment #8
elijah lynnYou would just "Run SQL query/queries on database". The question is what is the Query?
I know this is possible. I would like to do this too!
What is the Query to run?
Comment #9
gregglesDocumentation is available in http://drupal.org/node/252697
Comment #10
Rhino commentedYou do realize that does the opposite, right? Should we
mysql> update comments set notify = 1141431420 where timestamp < 0;?Comment #11
gregglesThe documentation describes how to do a very similar task and describes why the query elements are what they are.
People who want the opposite should 1) figure out the opposite elements to the query 2) write the docs.
Comment #12
Rhino commentedThanks so much for your outstanding help.