Patch (to be ported)
Project:
Inactive User
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
30 Jul 2008 at 12:13 UTC
Updated:
1 Nov 2014 at 15:06 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
ekrispin commentedComment #2
deekayen commentedI don't think I understand your initial suggestion. Setting it 0 would notify the user on every cron run from the start of the notification period until they're blocked. If I were to fill this request, I'd want to do it in such a way that notification could happen on every cron run as opposed to just 3 or 5 times (imagining 4 extra notification config forms).
Comment #3
ekrispin commentedI mean to set it to 0 when the specified period has elapsed SINCE THE LAST TIME THE USER WAS NOTIFIED (not since his/her last access).
Comment #4
fred0 commentedIn reviewing this module for my site, I too realized I needed this functionality and that it wasn't much of a change to make it work. Here are patches against 6.x-1.0-beta2 for the install and module files that:
My preliminary testing shows it to work, but I'd love to get feedback from others. Since I haven't fully tested it, I would NOT recommend trying this patch on a live site.
I've also updated the Version for this issue to 6.x-10.beta2 since that is the version I patched against and since the issue was year old without update I assumed that interest in Drupal 5 updates had waned.
Comment #5
fred0 commentedI should also note that this currently sends notifications infinitely until the function is disabled whereas the original module only sent 1 notification. I'm considering adding a max number of notifications to send, but haven't gotten to it yet.
Comment #6
fred0 commentedMinor tweak to the wording on the new field descriptions.
Comment #7
deekayen commented