here's what i'm seeing in admin (screenshot attached)

CommentFileSizeAuthor
#5 notificationssettingsTOP.jpg65.28 KBzilla
#5 notificationsettingBottom.jpg44.53 KBzilla
screen-2.jpg29.31 KBzilla

Comments

kbahey’s picture

kbahey commented
Status: Active » Fixed

Fixed. Should be in a new tar ball in 12 hours.

zilla’s picture

zilla commented

thanks.

btw, how does this interact with standard message settings (meaning if i don't touch any of that stuff, just leave cron percentage and others at zero)

kbahey’s picture

kbahey commented

The module has no settings of its own.

You must have cron running every hour at least.

zilla’s picture

zilla commented

thanks, i think i've set it to every 3 hours right now (just a dev site, only me)

zilla’s picture

zilla commented
StatusFileSize
new notificationsettingBottom.jpg44.53 KB
new notificationssettingsTOP.jpg65.28 KB

it's working - got it enabled...marking as fixed BUT with a fup question...attached is a screenshot (two for top and bottom) of my 'notifications settings' - there's a confusing line about 'immediate sending' where if you check it, it would appear to disable! is that correct? with your module installed, will this in turn handle such cron tasks? i'm a bit unclear about where else in drupal the cron tasks are running (in core, if at all) - or if this supports handlign for modules like comment notify (provided they make use of job queue!)

attached are the items (i think by turning off immediate sending i am duplicating the functionality of this module??)

kbahey’s picture

kbahey commented

attached is a screenshot (two for top and bottom) of my 'notifications settings' - there's a confusing line about 'immediate sending' where if you check it, it would appear to disable! is that correct? with your module installed, will this in turn handle such cron tasks? i'm a bit unclear about where else in drupal the cron tasks are running (in core, if at all) - or if this supports handlign for modules like comment notify (provided they make use of job queue!)

Cron is necessary for many things. You have to have it enabled otherwise you have logs that grow, search indexing stops, and many other bad things.

Notification has its own framework, and I had issues with another module because they use drupal_mail_send() and not drupal_mail().

However, I think under Drupal 6 queue_mail will still takeover and override notifications and do the sending itself, via job queue.

I have not tried that combination, nor can I test every combination of every module out there.

So the best answer is to try it yourself.

zilla’s picture

zilla commented

ah - that's why that setting is in there for notifications!! i remember that issue from ages ago!! you'd post a node or comment, and before it could run it would check against all known subscriptions to that content type for notifications (same issue with subscriptions if i recall) -and so now it can be disabled and kicked out to run alongside cron, which makes it sound like (intuitively) queue mail should take over if it's being passed off to cron and away from notification's own handlers...or does that sound ludicrous? i have no idea what i'm talking about now, gotta go put the dogs out... ;)

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.