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

[Bug 39807] New: Problems with search bar on intranet mainpage for users with limited permissions
by bugzilla-daemon＠bugs.koha-community.org 13 Dec '25

13 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39807 Bug ID: 39807 Summary: Problems with search bar on intranet mainpage for users with limited permissions Change sponsored?: --- 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: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com To recreate: 1. Make or find a staff member with staff access and list_borrowers permission. 2. Visit the intranet mainpage and notice the 'Search catalog' label but there is no search box. 3. Click 'Search catalog', the search bar now appears 4. Add the 'edit_borrowers' permission 5. Revisit the intranet mainpage and notice both 'Search patrons' and 'Search catalog' links 6. Click on 'Search catalog', now you see both search bars stacked up. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 31113] New: Permission change to so user can use marc modification template only when adding or editing single record
by bugzilla-daemon＠bugs.koha-community.org 12 Dec '25

12 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31113 Bug ID: 31113 Summary: Permission change to so user can use marc modification template only when adding or editing single record Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: aspencatteam(a)clicweb.org QA Contact: testopia(a)bugs.koha-community.org Would like to see a permission to allow the application of marc modification template to single record, without having the permission to do batch record modification. This would allow admin to create marc modification template that a novice cataloger could use to supply certain fields they probably would not know to change. (Like in leader, 008, 007). We would not want them to be able to do batch record modification - just use template on single record. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 9762] Log circulation overrides
by bugzilla-daemon＠bugs.koha-community.org 12 Dec '25

12 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9762 David Nind <david(a)davidnind.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |david(a)davidnind.com --- Comment #123 from David Nind <david(a)davidnind.com> --- Fantastic video about this change from Nick and Jessie on ByWater Solutions' Monday Minutes https://zurl.co/PKMDz -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 41433] New: Generating an API key for a vendor should include API url
by bugzilla-daemon＠bugs.koha-community.org 12 Dec '25

12 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41433 Bug ID: 41433 Summary: Generating an API key for a vendor should include API url Initiative type: --- Sponsorship --- status: 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: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com It would be helpful when we are generating the API key for a vendor if it would also display the API url along with the ID and secret. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 41442] New: check_api_auth can fail to authenticate service user if userid is not same as cardnumber
by bugzilla-daemon＠bugs.koha-community.org 12 Dec '25

12 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41442 Bug ID: 41442 Summary: check_api_auth can fail to authenticate service user if userid is not same as cardnumber Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: gmcharlt(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org If check_api_auth() ends up doing internal authentication of a service user whose userid is not the same as its cardnumber, the password can get successfully validated but the overall authentication can fail. This is because, like other authentication pathways, it's possible to pass a cardnumber to identify the user to check_api_auth() and have checkpw() successful validate the password. However, after checkpw() is called, the authentication must pass haspermission(), which _requires_ that it always be passed the userid. Other authentication pathways will result in $userid getting set correctly before it's passed to haspermission(), but check_api_auth() doesn't currently do that. One way that this can manifest is that if you have set up a service user for the OCLC Connexion importer whose cardnumber is not the same as the userid, the importer's attempts to authenticate itself to Koha can subtly fail. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 31323] New: Edit item highlighting problem
by bugzilla-daemon＠bugs.koha-community.org 12 Dec '25

12 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31323 Bug ID: 31323 Summary: Edit item highlighting problem Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl To reproduce: 1 search the catalog 2 find a record with 1 item 3 click the edit button in the item table (to the right of Spine Label) 4 when I click "save changes" the item is still highlighted yellow It appears like the '.active' class is lingering. I think this might be caused by Bug 27526? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 19

[Bug 41441] New: Add price column to suggestion table
by bugzilla-daemon＠bugs.koha-community.org 12 Dec '25

12 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41441 Bug ID: 41441 Summary: Add price column to suggestion table Initiative type: --- Sponsorship --- status: 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: michaela.sieber(a)kit.edu QA Contact: testopia(a)bugs.koha-community.org The price does not appear in the list of suggestions but it would be very helpful! To reproduce: 1.) Go to Suggestions (cgi-bin/koha/suggestion/suggestion.pl) 2.) Enter a new purchase suggestion with a Title and some acquisition data like price & currency, fund and copies 3.) verify that there is already a column for fund, but there are no columns for price, currency and copies -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 10190] Overdue notice triggers based on item type
by bugzilla-daemon＠bugs.koha-community.org 12 Dec '25

12 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10190 --- Comment #204 from Jonathan Druart <jonathan.druart(a)gmail.com> --- In the last patch: - min; + `${min}`; Why this kind of changes exactly? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 39287] New: Improve "Show volume" search with a more specialized search index
by bugzilla-daemon＠bugs.koha-community.org 12 Dec '25

12 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39287 Bug ID: 39287 Summary: Improve "Show volume" search with a more specialized search index Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl, michaela.sieber(a)kit.edu Currently the rcn index used to search for volumes contains all $w subfields from 7xx and 8xx linking fields. In some cases this is too broad, even tho we are additionally limiting to monographs. Example: Search volumes will also find - records with a 775$w - other edition - records with a matching 780/785$w - preceeding or succeeding ... A specific index for searching volumes (rcn-volumes) should contain: - 773$w (we still need to limit to monographic, because these could also be analytcal links) - 800$w - 810$w - 811$w - 830$w Once the index is defined we can update the XSLT and the method for determining if the "Show volumes" link should be shown to use it and have a correct result list. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 41303] New: "showRDAtag264" not displayed in staff client detail page and not fully in OPAC
by bugzilla-daemon＠bugs.koha-community.org 12 Dec '25

12 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41303 Bug ID: 41303 Summary: "showRDAtag264" not displayed in staff client detail page and not fully in OPAC Initiative type: --- Sponsorship --- status: Product: Koha Version: 24.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: anke.bruns(a)gwdg.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com The subfields (typically a, b, c) of 264 are not preceded by any description like e.g. Place of Publication: Publisher: Publication Date: Or even a single description like Publication details: as seems to be the case if these are stored in 260 (see XSLT) In the OPAC they are preceded by "Publisher" but then no further specification as to place, date or publisher. I think the passage in the relevant Detail page XSLT overwritten  and the corresponding template showRDAtag264 are probably the thing to look at. How to fix this? (Maybe this is related to https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37423 ). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2