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

[Bug 20844] New: Reset a hold when it is missing after allocation
by bugzilla-daemon＠bugs.koha-community.org 29 Apr '26

29 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20844 Bug ID: 20844 Summary: Reset a hold when it is missing after allocation Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: hughr(a)brimbank.vic.gov.au QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com There currently is no simple way to 'deallocate' a hold if it has gone missing after it is allocated to a patron but before they collect it. This enhancement would work as follows: 1. item is allocated 2. item cannot be located when patron tries to collect it 3. staff member marks item as Lost 4. if hold was originally a bib-level hold, hold reverts from being specific to the missing item, back to a bib-level hold with priority 1. 5. if hold was originally item-level, staff member gets an alert asking whether to cancel or retain the hold 6. (optionally?) a 'lost hold' notice is queued to be sent to the patron This bug is related to the original description of https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19287#c32 and also to https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15679 To do it properly, it may require a couple of new settings, something like: LostBibLevelHoldsRevert SendLostHoldNotices -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 150

[Bug 38399] New: Create a script that lists records that are not linked to any authority
by bugzilla-daemon＠bugs.koha-community.org 29 Apr '26

29 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38399 Bug ID: 38399 Summary: Create a script that lists records that are not linked to any authority Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: enica(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz It would be nice to have a script that would list which bibliographic records are not linked to any authorities. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 38327] New: 403 errors when logging back into Koha.
by bugzilla-daemon＠bugs.koha-community.org 29 Apr '26

29 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38327 Bug ID: 38327 Summary: 403 errors when logging back into Koha. Change sponsored?: --- Product: Koha Version: Main 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: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Firstly, I have been unable to recreate this issue myself, either in a production environment or in k-t-d. Many libraries are reporting 403 errors after signing back into Koha. The only remedy seems to be clearing the browser cache. This is happening to sessions in the staff client but also happening frequently in the SCO module. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 28

[Bug 39730] New: Remove GetUnprocessedSuggestions from C4/Suggestions.pm
by bugzilla-daemon＠bugs.koha-community.org 29 Apr '26

29 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39730 Bug ID: 39730 Summary: Remove GetUnprocessedSuggestions from C4/Suggestions.pm 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: baptiste.wojtkowski(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org See https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23990 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14

[Bug 39716] New: Warn when saving a notice with template toolkit errors
by bugzilla-daemon＠bugs.koha-community.org 28 Apr '26

28 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39716 Bug ID: 39716 Summary: Warn when saving a notice with template toolkit errors 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: lisette(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When a notice is saved with unusable template toolkit, we should warn even if not using the "save and continue editing" button, such as redirecting back to the page with the error. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 40240] New: Improve visibility for error when saving notices
by bugzilla-daemon＠bugs.koha-community.org 28 Apr '26

28 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40240 Bug ID: 40240 Summary: Improve visibility for error when saving notices Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: marion.durand(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Bug 31211 add a validation system to detect error in notification template when saving. Currently, it displays a message for certain type of fault, but the error message is really easy to miss. It is an additional message on the page, not a modal, and it doesn't prevent to save. So if you just click on "Save", it will save and take you back to the list of all notices without showing anything. If you click on "Save and continue editing", you then have to display again the message transport type just updated to see the error. So you need to be actively looking for the message to see it. We could probably use a modal that warn about the error and offer a choice between saving as it is or go back to editing. To reproduce : 1- Go to Tools > Notification 2- In any notification template, enter the following model (note the missing END) ``` Hello, [% FOREACH biblio IN biblios %] ``` 3- Click on "Save and continue editing", you stay on the same page but the section (message transport type for instance Email) is now collapsed 4- Click on the section you just edited, you now have a field "Template Toolkit error" that warn about the error 5- Repeat setp 1 and 2 6- Click on "Save" 7- You have not been warned about the error 8- Go back to the same notification, and click the appropriate section, the warning is still there. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 25122] New: Authority lookup shouldn't include non-authority fields
by bugzilla-daemon＠bugs.koha-community.org 28 Apr '26

28 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25122 Bug ID: 25122 Summary: Authority lookup shouldn't include non-authority fields 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: phil(a)chetcolibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Bug 21826 taught the linker that it should only consider certain subfields while looking for a match and while creating authority records, but authority lookup from the plugin link in the basic editor or from ctrl+shift+L in the advanced editor still considers them. Given "700 1_ $aBurns, Ken,$d1953-$etelevision director,$etelevision producer." the linker will search for an authority without the director/producer bits and if it doesn't find a match will create an authority without them, but ctrl+shift+L will fill the Search main heading search field with "1953- television director, television producer." -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 30312] New: letter.pl All libraries selection should only show All libraries
by bugzilla-daemon＠bugs.koha-community.org 28 Apr '26

28 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30312 Bug ID: 30312 Summary: letter.pl All libraries selection should only show All libraries Change sponsored?: --- Product: Koha Version: 21.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org This page drives me nuts. It would be appreciated if the "All libraries" selection would only show the templates that are for (All libraries). Maybe it should be changed to "Defaults" to show (All libraries), and have the (All libraries) show everything. Either way, it would be helpful to change this so you could see it one way or the other. The way it is now is maddening. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 11

[Bug 25390] New: Login box is removed from opac-main.tt if Shibboleth or CAS is enabled
by bugzilla-daemon＠bugs.koha-community.org 27 Apr '26

27 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25390 Bug ID: 25390 Summary: Login box is removed from opac-main.tt if Shibboleth or CAS is enabled 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: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org On the OPAC main page (opac-main.tt) if CAS or Shibboleth are enabled than we remove the login box on the right side of the page (#login). I am wondering if this is necessary: 1. It does not remove local login functionality as you can still login via the modal in the top right corner. 2. In multi library systems this can be a problem as some might use a SSO service while others would like to see the login box on the right side. 3. Maybe it would be simpler to keep the login box regardless of sign in method and hide it via CSS for libraries that don't want it? -- You are receiving this mail because: You are watching all bug changes.

1 13

[Bug 39961] New: koha-create doesn't start all queues
by bugzilla-daemon＠bugs.koha-community.org 27 Apr '26

27 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39961 Bug ID: 39961 Summary: koha-create doesn't start all queues Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Installation and upgrade (command-line installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com To reproduce: 1. Run: $ ktd --shell k$ sudo koha-create --create-db test => FAIL: No mention to `long_tasks`: ``` Koha instance is empty, no staff user created. Restarting Apache httpd web server: apache2. Starting Koha worker daemon for test (default):. Starting Koha indexing daemon for test:. ``` -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 24