Bug 11318 - Overdues won't send if first trigger lacks a delay value
Summary: Overdues won't send if first trigger lacks a delay value
Status: RESOLVED MOVED
Alias: None
Product: Koha
Classification: Unclassified
Component: Notices (show other bugs)
Version: unspecified
Hardware: All All
: P5 - low minor (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
: 11892 (view as bug list)
Depends on:
Blocks:
 
Reported: 2013-11-28 05:51 UTC by David Cook
Modified: 2020-04-28 20:45 UTC (History)
2 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Cook 2013-11-28 05:51:00 UTC
Overdue notices will not send if the first overdue trigger lacks a delay value (i.e. if the delay1 field in the overduerules table table is null).

It doesn't matter if your second and third triggers are set with notices and values. If you have a notice and no value for the first, that's it - nothing.

This behaviour has a certain logic to it, I suppose, but as Katrin has pointed out, it could perhaps fail nicer and print a message saying there are other triggers set but they can't be reached since the first one is null.
Comment 1 Katrin Fischer 2015-06-07 10:43:54 UTC
Still valid.
Comment 2 Katrin Fischer 2020-01-05 12:53:04 UTC
*** Bug 11892 has been marked as a duplicate of this bug. ***
Comment 3 Katrin Fischer 2020-04-28 20:45:04 UTC
I believe it's no longer possible to configure a null value from the GUI, see also bug 25049 (and verified in testing). I think best to focus on bug 25049 now and add good error messages there.