Bug 21508 - lost item phrase is repeated on pay fines page, when a patron is charged after an item is changed to lost
Summary: lost item phrase is repeated on pay fines page, when a patron is charged afte...
Status: CLOSED FIXED
Alias: None
Product: Koha
Classification: Unclassified
Component: Fines and fees (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-10-06 10:26 UTC by Koha Team University Lyon 3
Modified: 2025-06-02 20:46 UTC (History)
2 users (show)

See Also:
GIT URL:
Initiative type: ---
Sponsorship status: ---
Comma delimited list of Sponsors:
Crowdfunding goal: 0
Crowdfunding committed: 0
Crowdfunding contact:
Patch complexity: String patch
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Koha Team University Lyon 3 2018-10-06 10:26:20 UTC
The preference system WhenLostChargeReplacementFee = charge
On the tab fines, pay fines (/members/pay.pl), when a patron is charged automatically because an item he has borrowed is changed to lost status, the test repeats "lost iem" twice in the column description :
Lost item , Lost Item + Title
Comment 1 David Nind 2024-06-08 05:10:16 UTC
From what I can see, this is fixed in main:
1. Make sure WhenLostChargeReplacementFee is set to "Charge".
2. Check out an item to a patron.
3. Make sure that the item has a value in $v - Cost, replacement price.
4. Edit the item so that $1 - Lost status is set to "Lost".
5. Go to the patron's account and select Accounting > Make a payment
6. There should be a charge for the lost item:
   . The account type column has 'Lost item' as the value
   . The description column does not have "lost item" shown twice - it has the title and barcode, and the title again in brackets,

There have been a lot of changes to the account/charges area since 2018, so I haven't tried to track down where it was fixed.