Scenario:

1) On January 1st, the admin user sets digest to go out every six months. Newsletter is schedule to go out on June 1.
2) On March 1st, admin changes his mind and decided to send out daily digest.
3) The digest window will then be set to send newsletters from jan 1 to jan 2 on the next cron run, from jan 2 to jan 3 on the next cron run, jan 3 to jan 4 on the next, etc. This will continue until the window catches up to the current date. This will bombard users with email.

What should instead happen is that all the nodes created between jan 1 and mar 1 get mailed out on the next cron job. Logic needs to be created to handle this.

Comments

Steve Dondley’s picture

Steve Dondley commented
Priority: Minor » Normal
Morris Singer’s picture

Morris Singer commented
Status: Active » Fixed

I have fixed this by having nodes dequeue when the digest window is altered. The user gets plenty of warning and the chance to change his mind. This is the best alternative I could figure, because the alternatives were the existing behavior or overly long digests when the window changes.

Changes may be found in the most recent development snapshot.

Status: Fixed » Closed (fixed)

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