Closed (fixed)
Project:
User Expire
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Reporter:
Created:
11 Oct 2015 at 14:04 UTC
Updated:
10 Nov 2015 at 17:04 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
gregglesOK, I'm going to work on this.
Comment #3
gregglesComment #4
kscheirerrun within the last @hours hours, where @hours is user_expire_warning_frequency / 60 * 60. Should match comment.
"is due to be blocked" might be shorter as "will be blocked".
Would also be nice to include an estimate for when the blocking would occur, although since this is via cron a specific time is impossible.
Comment #5
gregglesI thought about that too, but it felt like calculating it would be a pain :)
This patch fixes the two main things you noted.
Comment #8
gregglesI think the patch apply failure is from me committing a little too fast.
The current dev branch passes tests, so this is good.