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

[Bug 34051] New: Koha::AuthorisedValues->get_description_by_koha_field not caching results for non-existent values
by bugzilla-daemon＠bugs.koha-community.org 31 Jul '25

31 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34051 Bug ID: 34051 Summary: Koha::AuthorisedValues->get_description_by_koha_field not caching results for non-existent values 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: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org As I note at https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31216#c5 Koha::AuthorisedValues->get_description_by_koha_field isn't caching database results for non-existent values. Many authorised values lists don't have a value for 0, but many records contain values of 0. Koha::AuthorisedValues->get_description_by_koha_field() will do a database call every time it encounters a value that doesn't exist in the AV table, because it isn't caching the empty/null that is calculated based on the incoming value not existing in the AV table. In terms of code, it is a simple change, but Koha::AuthorisedValues->get_description_by_koha_field is used in a lot of places, so obviously we'll want to be careful making any changes. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 23

[Bug 36891] New: Restore returning 404 from svc/bib when the bib number doesn't exist
by bugzilla-daemon＠bugs.koha-community.org 30 Jul '25

30 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36891 Bug ID: 36891 Summary: Restore returning 404 from svc/bib when the bib number doesn't exist Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: phil(a)chetcolibrary.org Reporter: phil(a)chetcolibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Prior to bug 29697, svc/bib used GetMarcBiblio which returned undef if the requested bib number didn't exist, and returned a 404 if the record was undefined. That was switched to using Koha::Biblios->find, which returns undef if the bib number doesn't exist, and then calling undef->metadata->record, which doesn't go well. The if (defined $record) just needs to move up a line and be if (defined $biblio) on the return from the call that actually does return undef. -- You are receiving this mail because: You are watching all bug changes.

1 27

[Bug 37212] New: Advanced editor should warn the user when it loads a blank record after being passed an invalid bib number
by bugzilla-daemon＠bugs.koha-community.org 30 Jul '25

30 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37212 Bug ID: 37212 Summary: Advanced editor should warn the user when it loads a blank record after being passed an invalid bib number 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: phil(a)chetcolibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Depends on: 24424, 36891 Bug 24424 taught the advanced editor to load a blank record when it can't load the biblionumber passed to it, but because svc/bib wasn't actually returning 404 when the problem was not-found, it couldn't add a message to the user saying what went wrong. Now that bug 36891 has restored the return of 404, it can. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24424 [Bug 24424] Advanced editor - interface hangs as "Loading" when given an invalid bib number https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36891 [Bug 36891] Restore returning 404 from svc/bib when the bib number doesn't exist -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 26929] New: Koha will only display the first 20 macros Advanced Editor
by bugzilla-daemon＠bugs.koha-community.org 30 Jul '25

30 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26929 Bug ID: 26929 Summary: Koha will only display the first 20 macros Advanced Editor Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: nick(a)bywatersolutions.com Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl In 20.05, if a library has more than 20 macros, then they will not appear on the screen and will not be accessible to the cataloger. The current workaround, upping the value in this system preference, RESTdefaultPageSize - increased to 40, this will display the rest of the macros (over 20) for the library. -- You are receiving this mail because: You are watching all bug changes.

1 20

[Bug 36320] New: Clicking Edit items from catalogue/detail.pl leads to 'Add item' screen
by bugzilla-daemon＠bugs.koha-community.org 30 Jul '25

30 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36320 Bug ID: 36320 Summary: Clicking Edit items from catalogue/detail.pl leads to 'Add item' screen Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal 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 recreate: 1. Find a record with more than 1 items attached. 2. From catalogue/detail.pl click the 'Edit' button in the toolbar to activate the dropdown. 3. Click 'Edit items'. 4. This cannot direct the user to any particular item to edit because Koha doesn't know which item you want to edit at this point. If there is a single item this should direct the user straight to an 'Edit item'. If a record has many items maybe a blank screen ( no Add Item ) would be less confusing? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 30

[Bug 34614] New: Ability to restrict access to a digital item and access would be password protected
by bugzilla-daemon＠bugs.koha-community.org 30 Jul '25

30 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34614 Bug ID: 34614 Summary: Ability to restrict access to a digital item and access would be password protected Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Course reserves Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org It would be nice if there was a way to password-protect specific digital items within the collection. This would allow only a specific group of patrons/individuals to have access to it. This would be helpful to academic libraries and also within the course reserve module. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 37052] New: Accessing/Running Reports
by bugzilla-daemon＠bugs.koha-community.org 30 Jul '25

30 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37052 Bug ID: 37052 Summary: Accessing/Running Reports Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: nglhelpdesk(a)cityofglasgowcollege.ac.uk QA Contact: testopia(a)bugs.koha-community.org At the moment the only way to limit access to reports is to limit permissions to run them. This means Staff either have the ability to run or not run any report. Would it be possible to limit access by User ID meaning that a more granular access level is possible. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 26

[Bug 20396] New: Omnibus: Koha Cleanup
by bugzilla-daemon＠bugs.koha-community.org 30 Jul '25

30 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20396 Bug ID: 20396 Summary: Omnibus: Koha Cleanup Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: gaetan.boisson(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Some parts of the interface are not really working and have been in this status for a long time, either because a feature is boken and hard to fix, or because it was never really implemented in the first place. Other parts are not really used and could be removed, HEA is helpful to determine these situations to some extent, but not everything can be seen there. This omnibus will be used to link tickets related to cleaning up parts of Koha that can be removed. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 46

[Bug 20411] New: Remove StaffDetailItemSelection system preference and make the feature always on
by bugzilla-daemon＠bugs.koha-community.org 30 Jul '25

30 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20411 Bug ID: 20411 Summary: Remove StaffDetailItemSelection system preference and make the feature always on Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: gaetan.boisson(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com This is always used according to HEA, and a very useful feature, i am not sure it makes sense to let the administrators choose to have it or not. Permissions are here also to make sure librarians won't batch delete items. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 34

[Bug 37078] New: Damaged Status not showing in detail.pl
by bugzilla-daemon＠bugs.koha-community.org 29 Jul '25

29 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37078 Bug ID: 37078 Summary: Damaged Status not showing in detail.pl Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation 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 in 24.05 and in master, after setting an item to damaged, this status does not appear in the detail.pl page. The damaged status does show if the item is checked out, it will appear in the patron's checkouts with the damaged status. It also will show when the item is checked in. If changing the item to LOST or Not for Loan, these values do show. It appears to only not show when applying the item to the damaged status. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 30