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

[Bug 28762] New: Item status shows incorrectly on course-details.pl
by bugzilla-daemon＠bugs.koha-community.org 02 Jun '25

02 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28762 Bug ID: 28762 Summary: Item status shows incorrectly on course-details.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Staff Client 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 To recreate: - create a course in course reserves, add an item to it. - confirm your item shows Available for its status on course-details.pl - edit your item to be withdrawn, lost, damaged, notforloan, and restricted use - reload course-details.pl, confirm it still shows available filed bug 28761 for this on the OPAC. On the OPAC, withdrawn, lost, and damaged *do* update the status. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 140

[Bug 39273] New: Search does not handle the diagnosis messages properly
by bugzilla-daemon＠bugs.koha-community.org 02 Jun '25

02 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39273 Bug ID: 39273 Summary: Search does not handle the diagnosis messages properly Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Z39.50 / SRU / OpenSearch Servers Assignee: koha-bugs(a)lists.koha-community.org Reporter: baptiste.wojtkowski(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Some requests to the BNF catalogue like hereafter one return a <diagnosis> tag, which break Koha's parsing: https://catalogue.bnf.fr/api/SRU?version=1.2&operation=searchRetrieve&query… -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[Bug 30699] New: Several id idx
by bugzilla-daemon＠bugs.koha-community.org 02 Jun '25

02 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30699 Bug ID: 30699 Summary: Several id idx Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org In koha-tmpl/intranet-tmpl/prog/en/includes/search_indexes.inc there is : <select class="advsearch" name="idx" id="idx"> But this include is used several times, so there are several id="idx". We should remove this id. -- You are receiving this mail because: You are watching all bug changes.

1 22

[Bug 35802] New: Note date when patron password was last changed
by bugzilla-daemon＠bugs.koha-community.org 02 Jun '25

02 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35802 Bug ID: 35802 Summary: Note date when patron password was last changed Change sponsored?: --- Product: Koha Version: master 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.m.hall(a)gmail.com It would be helpful if the patron data included when the password was last changed. We often have patrons unsure if they had changed their password, or when, and if we had a date, we would be able to tell if had ever been changed, or when it was last changed. This would be helpful so we don't have to dig through logs, and have the information on hand. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 37977] New: Fix some issues with labels in Inventory form
by bugzilla-daemon＠bugs.koha-community.org 30 May '25

30 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37977 Bug ID: 37977 Summary: Fix some issues with labels in Inventory form Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P3 Component: Templates Assignee: phil(a)chetcolibrary.org Reporter: phil(a)chetcolibrary.org QA Contact: testopia(a)bugs.koha-community.org Or for a more accurate summary, "Fix the easy issues with..." because the hard ones with presentation impacts will come in a separate bug. In Cataloging - Inventory, the labels for Collection and Call number classification scheme just don't have a for="" that matches the id of the input, the former by using the name rather than the id, and the latter because the input doesn't have an id. The labels for the Optional filters for inventory list or comparing barcodes section of authorized values have correct for attributes, but wonky ids on the inputs: instead of using the authorized value's id, a unique number, they use the authorized value's value, so if you have a value "1" for notforloan and lost and withdrawn and damaged, like you probably do, there are four duplicate ids and zero labels for any of them, since the labels are all using things like 1011, not 1. -- You are receiving this mail because: You are watching all bug changes.

1 17

[Bug 37869] New: Plugin hook before_send_messages not triggered for any messages sent without use of process_message_queue.pl
by bugzilla-daemon＠bugs.koha-community.org 30 May '25

30 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37869 Bug ID: 37869 Summary: Plugin hook before_send_messages not triggered for any messages sent without use of process_message_queue.pl Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Most messages in Koha are handled by process_message_queue.pl. This script calls before_send_messages which calls the plugin hook before_send_messages. This works for nearly all messages, but some messages like WELCOME notices are triggered immediately and do not way to for process_message_queue.pl to run. We should move the triggering of before_send_messages into SendQueuedMessages so it is always handled. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 32

[Bug 33690] New: Add ability to send welcome notice when creating patrons using the REST API
by bugzilla-daemon＠bugs.koha-community.org 30 May '25

30 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33690 Bug ID: 33690 Summary: Add ability to send welcome notice when creating patrons using the REST API Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com CC: tomascohen(a)gmail.com As an addition/alternative to Bug 30299, it would be nice to have the ability to send a welcome notice when creating patrons via the API. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 43

[Bug 34212] New: Bug 23336 follow-up
by bugzilla-daemon＠bugs.koha-community.org 30 May '25

30 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34212 Bug ID: 34212 Summary: Bug 23336 follow-up Change sponsored?: --- Product: Koha Version: master 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Jonathan highlighted a few clean ups and improvements just after push of bug 23336. I intend to take care of them here so we don't lose them on the bug itself. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 30979] New: Add ability for opac users to checkout to themselves
by bugzilla-daemon＠bugs.koha-community.org 30 May '25

30 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30979 Bug ID: 30979 Summary: Add ability for opac users to checkout to themselves Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org In some trusted environments libraries would like their users to self-issue without having to use the SCO or SIP checkouts. i.e. once logged in a user should have the ability to check out to themselves much like they already have the option to renew and place holds etc. -- You are receiving this mail because: You are watching all bug changes.

1 187

[Bug 33711] New: Refine the token passing mechanisms introduced in bug 23336
by bugzilla-daemon＠bugs.koha-community.org 30 May '25

30 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33711 Bug ID: 33711 Summary: Refine the token passing mechanisms introduced in bug 23336 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com CC: koha-bugs(a)lists.koha-community.org, tomascohen(a)gmail.com Depends on: 23336 Bug 23336 introduces an API workflow for checkouts by adding two endpoints.. one for availability that creates a token for confirmations that can then be used by the checkouts endpoint to verify that availability has been checked. Whilst I think the availability endpoint is worthwhile in it's own right, I think we could also send back the token in the 409 pre-condition failed response of the checkouts endpoint so one could use that single endpoint for double duty in the right circumstances. I also think we could work on how the confirmation token is sent to the endpoint.. it's currently a simple query param but may lend itself to being part of the x-koha-overrides header or another header? Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23336 [Bug 23336] Add an API endpoint for issuing an item to a patron -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes. You are on the CC list for the bug.

1 3