July 2023 - Koha-bugs - lists.koha-community.org

[Bug 31179] New: Duplicate item is duplicating internal item fields
by bugzilla-daemon＠bugs.koha-community.org 14 Sep '23

14 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31179 Bug ID: 31179 Summary: Duplicate item is duplicating internal item fields Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Duplicate item is intended to duplicate the visible cataloging fields of an item, however, currently it is duplicating the complete internal record of the item To recreate: 1 - find an item in Koha staff client, copy the barcode 2 - Issue this item to a patron 3 - Return to the record 4 - Edit items 5 - Click 'Actions->Duplicate' for the item in question 6 - Save the item 7 - Note in the items table above for that 'Total checkouts' 'Due date' etc. have been copied to new item -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 24

[Bug 30042] New: Remove Date::Calc use in cleanborrowers.pl
by bugzilla-daemon＠bugs.koha-community.org 14 Sep '23

14 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30042 Bug ID: 30042 Summary: Remove Date::Calc use in cleanborrowers.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 25

[Bug 34213] New: import_patrons.pl
by bugzilla-daemon＠bugs.koha-community.org 13 Sep '23

13 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34213 Bug ID: 34213 Summary: import_patrons.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: Igor.A.Sychev(a)mail.ru QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Option "-c" --confirm or --matchpoint? root@koha:/usr/share/koha/bin# perl import_patrons.pl --help Usage: import_patrons.pl --file /path/to/patrons.csv --matchpoint cardnumber --confirm [--default branchcode=MPL] [--overwrite] [--preserve-field <column>] [--preserve-extended-attributes] [--update-expiration] [--expiration-from-today] [--verbose] Options: -h|--help Prints a brief help message and exits -c|--confirm Confirms you really want to import these patrons, otherwise prints this help -f|--file Path to the CSV file of patrons to import -c|--matchpoint Field on which to match incoming patrons to existing patrons -d|--default Set defaults to patron fields, repeatable e.g. --default branchcode=MPL --default categorycode=PT -k|--preserve-field Prevent specified patron fields for existing patrons from being overwritten -o|--overwrite Overwrite existing patrons with new data if a match is found -p|--preserve-extended-attributes Retain extended patron attributes for existing patrons being overwritten -en|--email-new Send the WELCOME notice email to new users -ue|--update-expiration If a matching patron is found, extend the expiration date of their account using the patron's enrollment date as the base -et|--expiration-from-today If a matching patron is found, extend the expiration date of their account using the patron's enrollment date as the base -v|--verbose Be verbose Multiple -v options increase the verbosity 2 repetitions or above will report lines in error 3 repetitions or above will report feedback -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 34340] New: Point of Sale email template is showing 0.00 in the Tendered field
by bugzilla-daemon＠bugs.koha-community.org 13 Sep '23

13 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34340 Bug ID: 34340 Summary: Point of Sale email template is showing 0.00 in the Tendered field Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: Laura.escamilla(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 18

[Bug 34334] New: Item(s) in MARCdetail untranslatable
by bugzilla-daemon＠bugs.koha-community.org 13 Sep '23

13 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34334 Bug ID: 34334 Summary: Item(s) in MARCdetail untranslatable Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: I18N/L10N Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: frederic(a)tamil.fr I'm trying to find the string Item(s) for the items tab in the MARC view in the staff interface and it doesn't look like it's in the po files anymore. To get there: 1. View any record in the staff interface 2. Click "MARC" on the left --> Item(s) tab 3. Install new language 3.1. Run the following commands in the terminal (replace fr-CA by any language code) cd misc/translator ./translate install fr-CA 3.2. In the staff interface, go to Administration > System preferences 3.3. Search for language 3.4. Check the box for the new language 3.5. Click Save all I18N//L10N preferences 4. Switch the staff interface to the new language 5. Refresh the MARC view page --> Item(s) tab still in English 6. In the terminal, search the .po files for the "Item(s)" string --> String not in the files -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 18

[Bug 34316] New: account->add_credit adds tries to add wrong statistic type
by bugzilla-daemon＠bugs.koha-community.org 13 Sep '23

13 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34316 Bug ID: 34316 Summary: account->add_credit adds tries to add wrong statistic type Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org Found while debugging 33608 on a new failure in Items.t. It was a FK constraint on credit_id which was very misleading. Cause is an exception that was not rethrown in Accounts coming from a wrong statistic type and revealed now by new code in UpdateStats/Statistic.pm. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 28493] New: Make koha-passwd display the username
by bugzilla-daemon＠bugs.koha-community.org 13 Sep '23

13 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28493 Bug ID: 28493 Summary: Make koha-passwd display the username Change sponsored?: --- Product: Koha Version: 20.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Packaging Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org CC: mtj(a)kohaaloha.com The current output looks like this: sudo koha-passwd <site> Password for <site>: abc123 Press enter to clear the screen... But who remembers what the username looks like? It would be helpful to print this too, along with the password. (The format of the username is "koha_<site>".) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 22

[Bug 34279] New: overduefinescap of 0 is ignored, but overduefinescap of 0.00 is enforced
by bugzilla-daemon＠bugs.koha-community.org 13 Sep '23

13 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34279 Bug ID: 34279 Summary: overduefinescap of 0 is ignored, but overduefinescap of 0.00 is enforced Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When creating a circ rule, we can set overduefinescap to blank or 0 and no cap is enforced. If we edit that rule, the blank/0 is converted to "0.00" which perl considers true, thus zero-ing out any calculated fine. Considering we've always ignored an overdue fines cap of 0, we should also ignore 0.00. However, perl is evaluating it as a string which makes it true instead of false as 0 is. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 27

[Bug 32271] New: Overdue fines cap (amount) set to 0.00 when editing rule
by bugzilla-daemon＠bugs.koha-community.org 13 Sep '23

13 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32271 Bug ID: 32271 Summary: Overdue fines cap (amount) set to 0.00 when editing rule Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org I noticed that when I add a circulation rule, if I leave the Overdue fines cap (amount) field empty, it is displayed as 0.00. If I later edit this rule, the Overdue fines cap (amount) field is *set to* 0.00, even if that's not what I wanted. This causes the fines.pl script to charge no fine at all. To test: 0. Preliminary settings 0.1. finesMode system preference must be set to Calculate and charge 0.2. MaxFine system preference must be empty 0.3. In Tools > Calendar, today must not be a holiday 1. Add a circulation rule with fines but no fines cap 1.1. Go to Administration > Circulation and fines rules 1.2. Add or modify a circulation rule, make sure - There is a quantity in "Current checkouts allowed" - There is a number of days in "Loan period" - There is an amount in "Fine amount" - There is a number in "Fine charging interval" (usually 1) - "Overdue fines cap (amount)" is **empty** 1.3. Save the circulation rule --> Note that the amount in "Overdue fines cap (amount)" is displayed as 0.00 2. Checkout an item with a date in the past to create an overdue 2.1. Find an item barcode 2.1.1. Go to Item search 2.2.2. Click Search 2.2.3. Copy a barcode from the search results 2.2. Go to a patron's file 2.2.1. Go to Patrons 2.2.2. Click on "Search" 2.2.3. Click on a patron's name 2.3. Click on the "Check out" tab on the left of the patron's file 2.4. Click on the settings icon in the "Enter item barcode" field 2.5. Pick a due date in the past 2.6. Paste the item barcode in the field 2.7. Click "Check out" or press Enter 2.8. Click "Yes, check out" --> Patron should have an overdue 3. Run fines.pl 3.1. In a terminal, run ./misc/cronjobs/fines.pl 4. Check that the patron has fines 4.1. Go to the patron's file 4.2. Click on the "Accounting" tab on the left --> Patron should have a fine (accruing) 5. Modify the circulation rule, change any field except "Overdue fines cap (amount)" (let's say the quantity of current checkouts has gone up) 5.1. Go to Administration > Circulation and fines rules 5.2. Click "Edit" next to the rule created in step 1 --> Note that the amount in "Overdue fines cap (amount)" is 0.00 5.3. Change any setting except "Overdue fines cap (amount)", e.g. change Current checkouts allowed to another number 5.4. Click "Save" --> Note that the amount in "Overdue fines cap (amount)" is displayed as 0.00 6. Redo step 2 7. Redo step 3 8. Redo step 4 --> Note that the patron has no fine If Overdue fines cap (amount) is empty, it should display as empty (or "Unlimited"), and when we edit the rule, the field should still be empty and save as empty. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 56

[Bug 34133] New: ILL table should be sorted by request id descending by default
by bugzilla-daemon＠bugs.koha-community.org 13 Sep '23

13 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34133 Bug ID: 34133 Summary: ILL table should be sorted by request id descending by default Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com CC: pedro.amorim(a)ptfs-europe.com The table saves state, so a user can choose their own. The default should be newest requests first if a user does not set something -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 20