December 2024 - Koha-bugs - lists.koha-community.org

[Bug 38429] New: Ambigiuos patron category when adding a new guarantee
by bugzilla-daemon＠bugs.koha-community.org 24 Feb '26

24 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38429 Bug ID: 38429 Summary: Ambigiuos patron category when adding a new guarantee Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com To recreate: 1. Have multiple patron categories that are set to 'Can be guarantee'. 2. Go to a patron record and click '+ Add guarantee' 3. Look at how the patron category is set. 4. It defaults to the first one alphabetically, by code. In step 2, I think we need a dropdown that would prompt staff to choose the correct category. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 25

[Bug 38758] New: Make formatting date and datetime fields in notices a bit shorter/easier
by bugzilla-daemon＠bugs.koha-community.org 24 Feb '26

24 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38758 Bug ID: 38758 Summary: Make formatting date and datetime fields in notices a bit shorter/easier Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org Currently, date formatting in notices with the TT Date plugin is a bit user unfriendly since the plugin has very simplistic parsing that only works on datetime or timestamp fields but not on date only fields (like commonly used fields as borrower.dateexpiry or reserves.reservedate etc.) Should a user of Reports know that? (No.) So this works: [% date.format(borrower.updated_on, "%B %d, %Y") %] But this does not: [% date.format(borrower.dateexpiry, "%B %d, %Y") %] ERROR PROCESSING TEMPLATE: date error - bad time/date string: expects 'h:m:s d:m:y' But we can overcome that by doing something like (for both date as well as datetime): [% KohaDates.datetime_from_string(mydate).strftime("%B %d, %Y") %] # where e.g. mydate == borrower.dateexpiry Note that it is a bit long and somewhat complex (unfriendly). (And btw, datetime_from_string does not check the result of dt_from_string but just assumes to get a DateTime object.) What about the shorter and more intuitive (for both date and datetime fields): [% mydate.strftime("%B %d, %Y") %] Or giving yet another example with a locale different from the default en_US: [% KohaDates.datetime_from_string(mydate).set_locale('nl_NL').strftime("%d %B %Y") %] Would this not read better: [% mydate.strftime("%d %B %Y", "nl_NL") %] The proposed patch adds a TT virtual method strftime that can be run on scalars as in the examples above (for date and datetime). No mention of KohaDates needed, no chaining of set_locale. Wont crash on invalid dates, just passes the original value if date could not be parsed. And importantly, the former KohaDates constructs with strftime still work (going via DateTime->strftime), so backwards compatible. Shorter and easier! What do you think? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 26

[Bug 38622] New: Fix Koha sample data to include preferred_name
by bugzilla-daemon＠bugs.koha-community.org 24 Feb '26

24 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38622 Bug ID: 38622 Summary: Fix Koha sample data to include preferred_name Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Installation and upgrade (web-based installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 38620] New: Non-existent hc-sticky asset included in opac-tags
by bugzilla-daemon＠bugs.koha-community.org 24 Feb '26

24 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38620 Bug ID: 38620 Summary: Non-existent hc-sticky asset included in opac-tags Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 36557, 36694 [% Asset.js("lib/hc-sticky/hc-sticky.js") | $raw %] But it got removed by bug 36694 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36557 [Bug 36557] Improve logic and display of OPAC cart, tag, and lists controls https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36694 [Bug 36694] Remove HC Sticky library in favor of CSS -- You are receiving this mail because: You are watching all bug changes.

1 23

[Bug 38595] New: table settings behaviour broken on some tables at the OPAC
by bugzilla-daemon＠bugs.koha-community.org 24 Feb '26

24 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38595 Bug ID: 38595 Summary: table settings behaviour broken on some tables at the OPAC Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 38436 Problem highlighted by bug 38436. There is a JS error on some views with tables at the OPAC. Uncaught TypeError: table_settings.columns is undefined Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38436 [Bug 38436] Adjust code for column visibility (after DataTables upgrade) -- You are receiving this mail because: You are watching all bug changes.

1 20

[Bug 38594] New: Table settings for courses reserves not working at the OPAC
by bugzilla-daemon＠bugs.koha-community.org 24 Feb '26

24 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38594 Bug ID: 38594 Summary: Table settings for courses reserves not working at the OPAC Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: jonathan.druart(a)gmail.com Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 23

[Bug 38466] New: Kbart import is not working
by bugzilla-daemon＠bugs.koha-community.org 24 Feb '26

24 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38466 Bug ID: 38466 Summary: Kbart import is not working Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: ERM Assignee: jonathan.druart(a)gmail.com Reporter: mathsabypro(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: jonathan.druart(a)gmail.com, jonathan.field(a)ptfs-europe.com, martin.renvoize(a)ptfs-europe.com, matt.blenkinsop(a)ptfs-europe.com, pedro.amorim(a)ptfs-europe.com Created attachment 174646 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=174646&action=e… example of KBART file not imported Tested today in PTFS MARC21 Sandbox - eHoldings > Local > Packages: create a local package - eHoldings > Local > Titles > Import from KBART > import a kbart file (I tested with several from https://bacon.abes.fr/exporter.html site) > To the following local package: select the local package created before > Keep unchecked the checkbox "Create linked bibliographic record:" (the same issue is present if it checked) Submit During a few second the message "Submitting" appears, and that is all, the records are not imported I can see this error in Console : EHoldingsLocalTitlesKBARTImport.vue:159 Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'invalid_columns') at EHoldingsLocalTitles…RTImport.vue:159:42 -- You are receiving this mail because: You are watching all bug changes.

1 26

[Bug 36182] New: Add booksellerid column to holdings table
by bugzilla-daemon＠bugs.koha-community.org 24 Feb '26

24 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36182 Bug ID: 36182 Summary: Add booksellerid column to holdings table Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: pedro.amorim(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 51

[Bug 38477] New: Regression: new overdue fine applied incorrectly when using "Refund Lost Item Charge and Charge New Overdue Fine" option in circ rules
by bugzilla-daemon＠bugs.koha-community.org 24 Feb '26

24 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38477 Bug ID: 38477 Summary: Regression: new overdue fine applied incorrectly when using "Refund Lost Item Charge and Charge New Overdue Fine" option in circ rules Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Depends on: 30254 Bug 30254 fixed this something like this previously. We're seeing erroneous fines created for patrons who previously returned something on time. In production, this occurs when an item is marked lost while not checked out to a patron. When that item is later found and checked in, Koha finds the most recent checkout and generates an overdue fine using the current date as the return date of the item (even though the item was returned at some point in the past). Set these sysprefs: - FinesMode: Calculate and Charge - WhenLostForgiveFine: Forgive - WhenLostChargeReplacementFee: Charge In circ rules: - Have a rule that charges fines - Set Refund lost item replacement fee to "Refund lost item charge and charge new overdue fine" 1 - Have/create item with replacement price 2 - Check item out to patron 1, due date in past 3 - Run fines.pl 4 - confirm fines on patron 1 5 - mark item lost 6 - confirm replacement cost generated and fine forgiven on patron 1 7 - check item in 8 - confirm replacement cost forgiven and new fine generated on patron 1 9 - check item out to patron 2, due date in future 10 - check item in 11 - mark item lost (no replacement fee generated because item is not checked out) 12 - in database, update date_due for checkout to patron 2, set to a date in the past 13 - check item in 14 - confirm patron 2 now has a fine At step 12 we're pushing the date_due of the old issue into the past to make date_due<curdate(). In production, this comes up when there are days between steps 10 and 13. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30254 [Bug 30254] New overdue fine applied to incorrectly when using "Refund lost item charge and charge new overdue fine" option in circ rules -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 41

[Bug 38375] New: SIP2 syspref SIP2SortBinMapping is not working
by bugzilla-daemon＠bugs.koha-community.org 24 Feb '26

24 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38375 Bug ID: 38375 Summary: SIP2 syspref SIP2SortBinMapping is not working Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: lmstrand(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Sort bin rules in system preference SIP2SortBinMapping are not being used by the SIP server. This functionality has broken between the 23.11 and 24.05 versions. We are adding the mappings directly to the SIP2 server configuration XML file as a workaround in 24.05 for now since sort bin mappings still work using the sip config file. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 37