Bug 11725 - Longoverdue cron job seems to not want to charge anymore
Summary: Longoverdue cron job seems to not want to charge anymore
Status: CLOSED INVALID
Alias: None
Product: Koha
Classification: Unclassified
Component: Command-line Utilities (show other bugs)
Version: Main
Hardware: All All
: P3 major (vote)
Assignee: Galen Charlton
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-10 03:28 UTC by Liz Rea
Modified: 2014-12-07 20:03 UTC (History)
0 users

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 Liz Rea 2014-02-10 03:28:34 UTC
Test plan: 

Have a book issued to a borrower that is overdue (sometime before 366 days overdue.)

Run the longoverdue cron job in a way that the item will be marked as long overdue - I did mine as follows:
perl longoverdue.pl --lost 10=2 --mark-returned --charge 2 --confirm

That means: mark things that are 10 days overdue with lost value 2, return them from the borrower record, and charge the borrower the replacement cost for realsies.

I wasn't able to get the script to charge, I'm either doing it wrong (not apparent, according to the documentation), or it's been broken with the patch for bug 7639, as reverting those changes causes items to be correctly charged again.
Comment 1 Liz Rea 2014-03-05 21:55:06 UTC
I'm thinking that this might have been my user error - we'll assume so for now. :)