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

[Bug 37354] New: Bookings should respect circulation rules for max loan periods
by bugzilla-daemon＠bugs.koha-community.org 24 Aug '26

24 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37354 Bug ID: 37354 Summary: Bookings should respect circulation rules for max loan periods Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: caroline.cyr-la-rose(a)inlibro.com, david(a)davidnind.com, fridolin.somers(a)biblibre.com, gmcharlt(a)gmail.com, katrin.fischer(a)bsz-bw.de, kkrueger(a)cuyahogalibrary.org, kyle.m.hall(a)gmail.com, laurence.rault(a)biblibre.com, nick(a)bywatersolutions.com, testopia(a)bugs.koha-community.org, thibaud.guillot(a)biblibre.com Depends on: 34440 +++ This bug was initially created as a clone of Bug #36271 +++ The original bug for this took on a life of its own and became broader in scope adding a series of circulation rules for the bookings system I've cloned it here to propose my original more limited-in-scope solution using existing circulation rules for loan length * renewals count. --------------------------------------------------------------- Currently, bookings are on/off at the item level, but the booking period is entirely open meaning an item can be booked for any period. We should refine this to allow libraries to control the maximum length an item can be booked for. During the original development, I suggested perhaps we should set the maximum to the loan length of the item times the max renewals from the circulation rules.. However, I didn't get much feedback as to whether this was appropriate or whether people wanted a distinct rule for these items or another alternative. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34440 [Bug 34440] Add warm-up and cool-down periods to bookings -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 63

[Bug 43369] New: JS error when opacuserlogin is turned off
by bugzilla-daemon＠bugs.koha-community.org 24 Aug '26

24 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43369 Bug ID: 43369 Summary: JS error when opacuserlogin is turned off Initiative type: --- Sponsorship --- status: Product: Koha Version: 24.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- When opacuserlogin is turned off, there is a JS error in the console stemming from the OpenIDConnect code, because has-search-query doesn't exist. -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 43353] New: Value Gender is ignored in Patron quick-add form
by bugzilla-daemon＠bugs.koha-community.org 24 Aug '26

24 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43353 Bug ID: 43353 Summary: Value Gender is ignored in Patron quick-add form Initiative type: --- Sponsorship --- status: Product: Koha Version: 25.05 Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: hans.palsson(a)hkr.se QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com Target Milestone: --- When using Patron quick-add form the value for Gender is not stored and has to be added manually, if requested. To validate; 1. In system preferences, set PatronQuickAddFields to include sex (Gender). 2. Go to Patrons and choose Quick add new patron. 3. Fill all required fields including on gender option 4. Save the patron. 5. Observe on the patron details page that patron Gender is not displayed (not the value entered in quick add). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 41675] New: Username value is ignored in quick-add form
by bugzilla-daemon＠bugs.koha-community.org 24 Aug '26

24 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41675 Bug ID: 41675 Summary: Username value is ignored in quick-add form Initiative type: --- Sponsorship --- status: Product: Koha Version: 25.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: hans.palsson(a)hkr.se QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com When adding a patron with the quick-add form any value entered into the Username field is ignored. Instead a value based on first and last name (i.e. john.travolta) is stored. This should not be done, if entered the value should be stored as it is done using the New Patron form. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 24

[Bug 43368] New: Linear shelf meters: allow distinction between empty and full cabinets
by bugzilla-daemon＠bugs.koha-community.org 24 Aug '26

24 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43368 Bug ID: 43368 Summary: Linear shelf meters: allow distinction between empty and full cabinets Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Target Milestone: --- See dependency. If callnumbers from a specific callnumber range are not used in items, we know that the corresponding cabinets and shelves are free. How do we know that shelves are full? Which shelves still have space? This needs a bit more thought. And is proably only practical with reasonable estimates. But would be nice to have in terms of managing storage space. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 12278] Total amount of each invoice should be displayed in invoices page (parcels.pl)
by bugzilla-daemon＠bugs.koha-community.org 24 Aug '26

24 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12278 --- Comment #15 from Matt Blenkinsop <matt.blenkinsop(a)openfifth.co.uk> --- Addressed the error and found that it also occurs for the Item count and Items expected table. I've opened bug 43361 to cover this -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 12278] Total amount of each invoice should be displayed in invoices page (parcels.pl)
by bugzilla-daemon＠bugs.koha-community.org 24 Aug '26

24 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12278 Matt Blenkinsop <matt.blenkinsop(a)openfifth.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |43361 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43361 [Bug 43361] Invoice item counts increase for every subscription order -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 12278] Total amount of each invoice should be displayed in invoices page (parcels.pl)
by bugzilla-daemon＠bugs.koha-community.org 24 Aug '26

24 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12278 --- Comment #14 from Matt Blenkinsop <matt.blenkinsop(a)openfifth.co.uk> --- Created attachment 203990 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=203990&action=e… Bug 12278: (follow-up) Use invoice quantity to sum total Prevents additional orders from subscriptions from being swallowed into the invoice total calculation -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 12278] Total amount of each invoice should be displayed in invoices page (parcels.pl)
by bugzilla-daemon＠bugs.koha-community.org 24 Aug '26

24 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12278 Matt Blenkinsop <matt.blenkinsop(a)openfifth.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Failed QA |Passed QA -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 41794] New: Error 500 in http://192.168.1.12:8080/cgi-bin/koha/cataloguing/z3950_search.pl
by bugzilla-daemon＠bugs.koha-community.org 24 Aug '26

24 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41794 Bug ID: 41794 Summary: Error 500 in http://192.168.1.12:8080/cgi-bin/koha/cataloguing/z395 0_search.pl Initiative type: --- Sponsorship --- status: Product: Koha Version: 25.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: egpetridis(a)yahoo.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Created attachment 192677 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=192677&action=e… intranet-access.log When searching z39.50 targets simultaneously, sometimes we get an 500 error. No further information on what target's response makes koha raise the error. What could be done to * make koha report on the targets sucessfully queried, * make koha not stumble when encountering erroneous replies from z39.50 targets * make koha note in the logs the target raising the error. The following logs are not redacted, the search was repeated after clearing logs and doing an init 6, so that logs would be more readable. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 34