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

[Bug 42321] New: Breeding should handle empty results from SRU targets better
by bugzilla-daemon＠bugs.koha-community.org 26 Jul '26

26 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42321 Bug ID: 42321 Summary: Breeding should handle empty results from SRU targets better Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Z39.50 / SRU / OpenSearch Servers Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Currently we see lots of warnings on e.g. the Folio LOC SRU server like: LOC SRU record 3: 61 LOC SRU record 4: 0 LOC SRU record 5: 0 LOC SRU record 6: 0 LOC SRU record 7: 0 LOC SRU record 8: 0 LOC SRU record 9: 0 LOC SRU record 10: 0 LOC SRU record 11: 0 LOC SRU record 12: 0 LOC SRU record 13: 0 LOC SRU record 14: 0 LOC SRU record 15: 0 LOC SRU record 16: 0 LOC SRU record 17: 0 LOC SRU record 18: 0 LOC SRU record 19: 0 LOC SRU record 20: 0 These are just empty results. (Note in a larger perspective, we probably should not search those SRU targets via the (old) ZOOM object.) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 27

[Bug 38058] New: Backticks in vue files break translation script
by bugzilla-daemon＠bugs.koha-community.org 26 Jul '26

26 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38058 Bug ID: 38058 Summary: Backticks in vue files break translation script Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: I18N/L10N Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: f.demians(a)tamil.fr, jonathan.druart(a)gmail.com (In reply to Matt Blenkinsop from comment #61) > Created attachment 166571 [details] [review] > Bug 34788: (follow-up): Fix translations Please stop using backtick, it does not work correctly with translations. See: fr-FR-messages-js.po +#: koha-tmpl/intranet-tmpl/prog/js/vue/dist/erm.js:20920 +#, javascript-format +msgid "" +"Your file was too large to process in one job, the file has been split into %s jobs to meet the maximum size limits.\"\n" +" ).format(success.job_ids.length)}</p>`\n" +" }\n" +" success.job_ids.forEach((job, i) => {\n" +" message += `<li>${this.$__(\n" +" \"Job %s for uploaded file has been queued\"\n" +" ).format(\n" +" i + 1\n" [...] -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 27917] New: Make it clear that standing orders cannot create items at point of ordering
by bugzilla-daemon＠bugs.koha-community.org 26 Jul '26

26 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27917 Bug ID: 27917 Summary: Make it clear that standing orders cannot create items at point of ordering Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When creating a basket, one chooses whether one wants to create item records when ordering, when receiving, or when cataloging. If your basket is a standing order basket, then it cannot create items when ordering. Koha will allow you to pick "placing an order" for when to create items for a standing order basket, but then will not create the item. When creating a basket, we should not allow one to choose "placing an order" for "Create items when" if one has checked the Standing Order box. We should also not allow one to select default for "Create items when" when making a standing order basket if the AcqCreateItem syspref is set to "placing an order." -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14

[Bug 32968] New: Create granular permissions for ERM
by bugzilla-daemon＠bugs.koha-community.org 26 Jul '26

26 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32968 Bug ID: 32968 Summary: Create granular permissions for ERM Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ERM Assignee: jonathan.druart+koha(a)gmail.com Reporter: pedro.amorim(a)ptfs-europe.com CC: jonathan.druart+koha(a)gmail.com, jonathan.field(a)ptfs-europe.com, martin.renvoize(a)ptfs-europe.com, pedro.amorim(a)ptfs-europe.com Depends on: 32925 Currently, there is only one top-level permission for ERM on the system. Example: Allow a staff member to create agreements but not delete them. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32925 [Bug 32925] Display loading info when a form is submitted -- You are receiving this mail because: You are watching all bug changes.

1 82

[Bug 30956] New: Make 773 visible in default framework
by bugzilla-daemon＠bugs.koha-community.org 26 Jul '26

26 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30956 Bug ID: 30956 Summary: Make 773 visible in default framework Change sponsored?: --- Product: Koha Version: 20.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Bibliographic data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org 773 is used for EasyAnalytics and for creating child records in Koha and as such linked to specific functionalities, but by default, it's hidden in the default framework. We should make at least atng, maybe more subfields, visible (these are displayed in the detail pages). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 40000] New: Show patron is the anonymous in patrons search
by bugzilla-daemon＠bugs.koha-community.org 26 Jul '26

26 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40000 Bug ID: 40000 Summary: Show patron is the anonymous in patrons search Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Show patron is the anonymous in patrons search -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 37

[Bug 41639] New: OPAC cover images use non-descriptive alt text
by bugzilla-daemon＠bugs.koha-community.org 26 Jul '26

26 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41639 Bug ID: 41639 Summary: OPAC cover images use non-descriptive alt text Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Keywords: accessibility Severity: normal Priority: P5 - low Component: Accessibility Assignee: Laura.escamilla(a)bywatersolutions.com Reporter: Laura.escamilla(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: martin.renvoize(a)openfifth.co.uk, matt.blenkinsop(a)openfifth.co.uk, oleonard(a)myacpl.org Cover images displayed in the Koha OPAC currently use generic alt text values such as “Amazon Cover Image” and “Local Cover Image.” These values do not provide a meaningful text alternative for screen reader users and do not meet WCAG 2.2 AA Success Criterion 1.1.1 (Non-text Content). Because OPAC cover images are functional (they are clickable and serve as a visual identifier for bibliographic records), they cannot be considered decorative and therefore require a descriptive text alternative. -- You are receiving this mail because: You are watching all bug changes.

1 23

[Bug 31415] New: Script to automate converting reserves to recalls
by bugzilla-daemon＠bugs.koha-community.org 26 Jul '26

26 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31415 Bug ID: 31415 Summary: Script to automate converting reserves to recalls Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com If a record reaches X number of reserves, the library may convert reserves to recalls to prompt patrons to return them sooner. This can be automated with a script. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 38

[Bug 39455] New: Correct "cardnumber" to "card number" (when refering to the patron's card number, unless it's the database column)
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '26

25 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39455 Bug ID: 39455 Summary: Correct "cardnumber" to "card number" (when refering to the patron's card number, unless it's the database column) Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation 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: aude.charillon(a)ptfs-europe.com, philip.orr(a)lmscloud.de Bug 38979 changed "cardnumber" to "card number". We should change the instances in the manual also. *Note that if this refers to the database column, it should stay "cardnumber". Here are the occurrences (if you have a local copy of the manual, you can do `git grep "cardnumber"` and it will find all the occurrences of the string in all the files). NOTE: I have not filtered the results! Some should stay as is. administration.rst:| LC-cardnumber | 010$a | administration.rst: either "userid" or "cardnumber" are present in the mappings. administration.rst: If auto register is enabled, make sure the "userid" or "cardnumber" administration.rst: If auto register is enabled, make sure the "userid" or "cardnumber" apis_protocols.rst: <cardnumber is="uid" ></cardnumber> circulation.rst:|selfcheckout-logincardnumber| circulationpreferences.rst:cardnumber is scanned instead of an item barcode. circulationpreferences.rst: This should not be enabled if you have overlapping patron cardnumbers circulationpreferences.rst:- cardnumber circulationpreferences.rst: If using 'cardnumber' and enhancedcontentpreferences.rst:- cardnumber images.rst: :alt: Patron's brief information panel showing the patron's name, cardnumber, address, phone number, date of birth and age, email, category, home library, borrowernumber, date of last update and a message in red reading 'Account has been administratively locked'. Under the patron's information are the patron account tabs: Check out, Details (currently selected), Accounting, Routing lists, Circulation history, Holds history, Modification log, Notices, Statistics, and Purchase suggestions. images.rst: :alt: Patron's brief information panel showing the patron's name, cardnumber, address, phone number, date of birth and age, email, category, home library, borrowernumber, date of last update and a message in red reading 'Account has been locked'. Under the patron's information are the patron account tabs: Check out, Details (currently selected), Accounting, Routing lists, Circulation history, Holds history, Modification log, Notices, Statistics, and Purchase suggestions. images.rst: :alt: Holdings tab in a detailed record in the staff interface, the item is marked as checked out, with the name of the patron, their cardnumber and the due date images.rst: :alt: Warning message 'This item has been claimed as returned by' followed by the name and cardnumber of the patron and a button 'Resolve' images.rst:.. |selfcheckout-logincardnumber| image:: images/circ/selfcheckout/selfcheckout-logincardnumber.png images.rst: :alt: Place hold confirmation screen on the OPAC. Shows the patron's name and cardnumber, the title and author of the item to be placed on hold, a dropdown menu to choose the pickup location, a link to show more options and a button 'Confirm hold' images.rst: :alt: Place hold confirmation screen on the OPAC. Shows the patron's name and cardnumber, the title and author of the item to be placed on hold, a dropdown menu to choose the pickup location, a link to hide options, a date field 'Hold not needed after', an option to place the hold on the next available item or a specific item and a button 'Confirm hold' images.rst: :alt: Place hold confirmation screen on the OPAC. Shows the patron's name and cardnumber, the title and author of the item to be placed on hold, a dropdown menu to choose the pickup location, a link to hide options, a date field 'Hold not needed after', an option to place the hold on the next available item or a specific item, the specific item option is selected, and it is followed by a table of the record's items with the following columns: Copy number which contains the copy number as well as the selection box, Item type, Barcode, Home library, Last location, Collection, Call number, Notes and Information. At the botton of the page is a 'Confirm hold' button. images.rst: :alt: SQL field when creating a report from SQL, in the box, SELECT borrowers.ca is typed and suggestions for borrowers.cardnumber and borrowers.categorycode are displayed koha_spelling_wordlist.txt:cardnumber koha_spelling_wordlist.txt:cardnumbers logspreferences.rst: Enabling this system preference allows the tracking of cardnumber changes opac.rst:Patrons registered in this way will not have a cardnumber until assigned opac.rst:their identity before given a cardnumber and the ability to check items opac.rst:generating cardnumbers before providing them to self registered patrons. opac.rst:and add a cardnumber/barcode. opacpreferences.rst: Remember to use the borrowernumber not the patron's cardnumber for patrons.rst: able to search for any part of the patron's name or cardnumber. patronspreferences.rst:Default: firstname\|middle_name\|surname\|othernames\|cardnumber\|userid patronspreferences.rst:- cardnumber patronspreferences.rst:Default: surname\|cardnumber patronspreferences.rst:.. _cardnumberlength-label: patronspreferences.rst: (i.e., ^,Max'). If 'cardnumber' is included in the reports.rst: For example, to have the suggestion for :code:`cardnumber`, you must type reports.rst: SELECT cardnumber, reports.rst:Koha will automatically generate hyperlinks for any report that contains a borrowernumber, cardnumber, itemnumber or biblionumber. reports.rst:- cardnumber: Check out reports.rst: SELECT CONCAT('<a href=\"/cgi-bin/koha/members/boraccount.pl?borrowernumber=',borrowernumber,'\">', cardnumber, '</a>'), surname, firstname reports.rst: - :code:`cardnumber` - The borrower's barcode number queried from Koha. This is what will be visible to the user and comprise the clickable link. reports.rst:After running a report that contains itemnumbers, biblionumbers and/or patron cardnumbers tools.rst: cardnumber, surname, and all fields you have tools.rst:- Choose to match on 'cardnumber' or 'username' to prevent adding of tools.rst:load in a file of cardnumbers (one per line), choose from a :ref:`list of tools.rst:cardnumbers. tools.rst:Once you have the file loaded or the cardnumbers or borrowernumbers entered click 'Continue.' webservices.rst:This service can be used to embed barcode images into slips and notices printed from the browser, and to embed a patron cardnumber into the OPAC, among other possibilities. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 41516] New: Terminology: Change cardnumber to card number for system preference descriptions
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '26

25 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41516 Bug ID: 41516 Summary: Terminology: Change cardnumber to card number for system preference descriptions Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: david(a)davidnind.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Unless specifically referring to a database field, card number should be used (see the terminology guidelines (https://wiki.koha-community.org/wiki/Terminology#C) The descriptions for these three system preferences need updating to reflect this: - AutoSwitchPatron - CardnumberLog - SelfCheckoutByLogin -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 18