[Koha-bugs] [Bug 17470] New: overdue_notices.pl produces X emails with the SAME list of ALL overdue items if a patron has overdue items from X branches
bugzilla-daemon at bugs.koha-community.org
bugzilla-daemon at bugs.koha-community.org
Thu Oct 20 09:24:57 CEST 2016
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17470
Bug ID: 17470
Summary: overdue_notices.pl produces X emails with the SAME
list of ALL overdue items if a patron has overdue
items from X branches
Change sponsored?: ---
Product: Koha
Version: master
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P5 - low
Component: Notices
Assignee: koha-bugs at lists.koha-community.org
Reporter: theod at lib.auth.gr
QA Contact: testopia at bugs.koha-community.org
If patron P has two overdue items:
I1 from branch B1 and
I2 from branch B2,
then overdue_notices.pl will produce two emails coming from B1 and B2 that have
the same list of BOTH items I1 AND I2 in BOTH emails.
I believe that this is not an intended behavior and that each email coming from
each branch should show overdue items belonging to that respective branch only.
Steps to reproduce:
0/ Have (or create) at least two branches B1 and B2
1/ Make sure you're logged in with an account belonging to B1, or switch to
branch B1
2/ checkout item I1 (belonging to B1) to patron P (preferably while specifying
a due date < today)
3/ switch to branch B2
4/ checkout item I2 (belonging to B2) to patron P (preferably while specifying
a due date < today)
5/ make sure you have defined "Overdue notice/status triggers" for that patron
category, ie with Delay=1 so that "Overdue Notice" is selected and "Email" is
checked.
6/ from cli run 'perl ./misc/cronjobs/overdue_notices.pl' (optionally
specifying also '-library B1 -library B2')
7/ (at least) two new entries will be generated in message_queue DB table,
coming from different branches that have the SAME list of overdue items
8/ either see the 'content' field in these entries, or run 'perl
./cronjobs/process_message_queue.pl' to receive the actual emails (provided the
email is properly setup)
I have verified the same behavior with versions 3.20.x, 3.22.x and master (but
must also apply to all recent Koha versions).
--
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.
More information about the Koha-bugs
mailing list