http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12768
--- Comment #30 from Maxime Beaulieu <[email protected]> --- (In reply to Eivin Giske Skaaren from comment #29) > After applying the patch I was unable to set "Charge", "Default replacement > cost" or "Processing fee" for any item. > After manually altering the table with the commands in > a/installer/data/mysql/atomicupdate/bug_12768-update_schema_files.sql The update worked fine on my end and I was able to edit the values. Have you run the installer/data/mysql/updatedatabase.pl script? > When using the longoverdue.pl script the item is marked as Long overdue > (lost) but there is no fine shown for the patron. > When using the longoverdue.pl script the result is the same as in scenario > 1. There is no fine. Did you run longoverdue.pl with the -c option? --charge | -c This specifies what lost value triggers Koha to charge the account for the lost item. Replacement costs are not charged if this is not specified. Also, the patron can not be charged multiple times for losing the same item. Even if you writeoff / pay the fine, it's still there in the DB. C4/Accounts.pm 368 # first make sure the borrower hasn't already been charged for this item 369 my $sth1=$dbh->prepare("SELECT * from accountlines 370 WHERE borrowernumber=? AND itemnumber=? and accounttype='L'"); You will need to remove the lost status from the item and run something like this in MySQL if you want to test multiple times with the same borrower and item combination. DELETE from accountlines WHERE borrowernumber=#BORROWERNUMBER# AND itemnumber=#ITEMNUMBER# and accounttype='L'; -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
