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

[Bug 41939] New: REST API doesn't show phone number for libraries
by bugzilla-daemon＠bugs.koha-community.org 26 Oct '26

26 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41939 Bug ID: 41939 Summary: REST API doesn't show phone number for libraries Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: jheltibridle(a)rcplib.org QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com When making a call to the API endpoint /public/libraries/{library_id} the response should included the library phone number. When testing on my system, I get the following fields in my response: "address1" "address2" "address3" "city" "country" "email" "fax" "ill_email" "library_id" "name" "postal_code" "state" "url" The "phone" field seems to be missing. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 29236] New: Allow OPAC News / HTML Customization contents to be set for library groups
by bugzilla-daemon＠bugs.koha-community.org 23 Oct '26

23 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29236 Bug ID: 29236 Summary: Allow OPAC News / HTML Customization contents to be set for library groups Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org For the content sent to various OPAC pages/fields from the HTML Customizations interface (OPACNavRight, OPACHeader, etc), it would be helpful to be able to set those values for groups of libraries, rather than just individual libraries. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 24288] New: Add wording to authorized value interface to indicate valid code length
by bugzilla-daemon＠bugs.koha-community.org 23 Oct '26

23 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24288 Bug ID: 24288 Summary: Add wording to authorized value interface to indicate valid code length Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration 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 Several standard authorized values feed into fields that require a single character code (LOST, NOTFORLOAN, DAMAGED, RESTRICTED, WITHDRAWN). It'd be good to have some wording in the authorized value interface that would indicate this. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 43

[Bug 40999] New: Tie checkout of an itemtype to a patron attribute
by bugzilla-daemon＠bugs.koha-community.org 23 Oct '26

23 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40999 Bug ID: 40999 Summary: Tie checkout of an itemtype to a patron attribute 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: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com Many libraries require some variety of agreement form to be signed before patrons can borrow various itemtypes (laptops, hedge trimmers, other items that are expensive or potentially dangerous when misused). Many of these libraries define patron attributes to record whether or not a given patron has signed the relevant agreement is on file. It could be helpful to allow a library to tie an itemtype to a specific patron attribute, blocking checkout of that itemtype to any patron who does not have a "Yes" or 1 in that attribute. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 40286] New: Make C4::Auth::checkpw_internal use Koha::Patrons->find_by_identifier
by bugzilla-daemon＠bugs.koha-community.org 23 Oct '26

23 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40286 Bug ID: 40286 Summary: Make C4::Auth::checkpw_internal use Koha::Patrons->find_by_identifier Change sponsored?: --- Product: Koha Version: Main 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 Bug 40275 introduced this method and this is the missing place for refactoring. The current tests for this method include the creation of actually conflicting patrons, matching their userid and cardnumber respectively. As making the proposed change is indeed a behavior change, I file this report in order to discuss how to handle it properly. The other use cases are clear and already covered in bug 40275. The blocker for this is bug 33905, in which we need to decide how to ensure identifier uniqueness, and then get rid of the tests. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 35

[Bug 38757] New: Adding order from a staged file - "Some required subfields are unset"
by bugzilla-daemon＠bugs.koha-community.org 23 Oct '26

23 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38757 Bug ID: 38757 Summary: Adding order from a staged file - "Some required subfields are unset" Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: emily.lamancusa(a)montgomerycountymd.gov QA Contact: testopia(a)bugs.koha-community.org When ordering from a staged file that contains item data, we have the option to edit or confirm the individual items on the "Select to import" tab, or import all items with identical information from the "Item information" tab. When importing individualized item data from the "Select to import" tab, clicking Save triggers an error: "Some required subfields are unset". Setting the Koha item type in the "Item information" tab fixes this error - but it shouldn't be necessary to set the item type in that tab if all items in the "Select to import" tab already have an item type specified. To replicate: 1. Go to Acquisitions and find or open a basket 2. Click Add to basket 3. Click Add from new file 4. Upload a MARC file containing item data 5. When the upload completes, click "Add to basket" 6. In the "Select to import" tab that comes up by default, check the checkbox next to one or more titles in the file --> This will expand the item data for those titles 7. Look over the item data, and confirm that all items have a homebranch, holdingbranch, and item type defined 8. Click "Save" --> An error pops up: "Some required subfields are unset" 9. Navigate to the "Item information" tab 10. Select a value for y - Koha item type 11. Click "Save" again --> The orders are imported successfully -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 36801] New: Allow un-resolving of a catalog concern
by bugzilla-daemon＠bugs.koha-community.org 23 Oct '26

23 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36801 Bug ID: 36801 Summary: Allow un-resolving of a catalog concern Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl We didn't allow for re-opening a resolved catalog concern before, but with the introduction of the update status's I think we managed to change the logic a bit and the 'Update' button now displays. This effectively allows for re-opening a resolved ticket; However, the actual ticket state isn't properly updated and should be so the new state is properly reflected in the display table and filtering options. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 42526] New: Bib record of an title with a Cataloging Concern, click on the "Concerns" tab, and then click on the "Details" button under "Actions, " nothing happens
by bugzilla-daemon＠bugs.koha-community.org 23 Oct '26

23 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42526 Bug ID: 42526 Summary: Bib record of an title with a Cataloging Concern, click on the "Concerns" tab, and then click on the "Details" button under "Actions," nothing happens Initiative type: --- Sponsorship --- status: Product: Koha Version: 25.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: sam.young(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl We can access our Cataloging Concerns from our Koha homepage. However, if we navigate to the bib record of an title with a Cataloging Concern, click on the "Concerns" tab, and then click on the "Details" button under "Actions," nothing happens--the pop-up window does not appear. See screenshot for https://staff-fayetteville.bywatersolutions.com/cgi-bin/koha/catalogue/deta…. This Error appears: Uncaught TypeError: $(...).kohaSelect is not a function at HTMLDivElement.<anonymous> ( VM1501 display_ticke…5.1102000.js:135:27 ) at HTMLDivElement.dispatch ( jquery-3.6.0.min_25.1102000.js:2:43064 ) at v.handle ( jquery-3.6.0.min_25.1102000.js:2:41048 ) at Object.trigger ( jquery-3.6.0.min_25.1102000.js:2:71515 ) at HTMLDivElement.<anonymous> ( jquery-3.6.0.min_25.1102000.js:2:72110 ) at S.each ( jquery-3.6.0.min_25.1102000.js:2:3003 ) at s.fn.init.each ( jquery-3.6.0.min_25.1102000.js:2:1481 ) at s.fn.init.trigger ( jquery-3.6.0.min_25.1102000.js:2:72086 ) at Object.trigger ( bootstrap.bundle.min…5.1102000.js:6:5314 ) at On.show ( bootstrap.bundle.min….1102000.js:6:51861 ) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 21889] New: Include Staff Client entered Purchase Suggestions with System Preference maxopensuggestions
by bugzilla-daemon＠bugs.koha-community.org 23 Oct '26

23 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21889 Bug ID: 21889 Summary: Include Staff Client entered Purchase Suggestions with System Preference maxopensuggestions Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Currently only Purchase Suggestions made by patrons through the OPAC are the only suggestions counted in the system preference MaxOpenSuggestions. It would be nice if this system preference also connected to the staff client, so a purchase suggestion done on the patrons account by staff alerted the staff that the patron already had the maximum number of purchase suggestion allowed. At this time, even if a patron has maxed out the number of open purchase suggestions on the OPAC, a staff member can still enter more purchase suggestions for that patron through the staff client without knowledge of the maxopensuggestions being reached. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 27859] New: Marc export for search result
by bugzilla-daemon＠bugs.koha-community.org 23 Oct '26

23 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27859 Bug ID: 27859 Summary: Marc export for search result Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: glasklas(a)gmail.com This patch provides the option of exporting a search result as MARCXML or iso 2709. Ideally the export should be asynchronous but it was much trickier than first thought to fork and detach from Apache so gave that up for now. A link to the export is sent to the current user as an email as a simple way of delivering the response asynchronously (keeping it this way so don't have to refactor when/if the export is made asynchronous). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 114