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

[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 40520] New: PatronSelfRegistrationAgeRestriction doesn't save 'null'
by bugzilla-daemon＠bugs.koha-community.org 30 Jul '25

30 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40520 Bug ID: 40520 Summary: PatronSelfRegistrationAgeRestriction doesn't save 'null' Change sponsored?: --- Product: Koha Version: 25.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: sbrown(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org If I add an age to PatronSelfRegistrationAgeRestriction and save, but then want to remove the age to disable the system preference, 'null' won't save properly. I get a 'Nothing to save' message, and the original value is still enforced. If I then leave the page and later return to the system preference, the entry box appears null even though the original value is still being enforced. As a temporary (and unintuitive) workaround, I can save 0 and still self-register patrons of any age. -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 40354] New: Suggested bibliographic Z39.50 targets - could use some updating
by bugzilla-daemon＠bugs.koha-community.org 30 Jul '25

30 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40354 Bug ID: 40354 Summary: Suggested bibliographic Z39.50 targets - could use some updating Change sponsored?: --- Product: Koha Version: 24.05 Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: eric(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: aude.charillon(a)openfifth.co.uk, david(a)davidnind.com, philip.orr(a)lmscloud.de https://koha-community.org/manual/latest/en/html/administration.html#sugges… It doesn't appear that ACCESS PENNSYLVANIA 205.247.101.11:210 INNOPAC is open to the public anymore CUYAHOGA COUNTY PUBLIC webcat.cuyahoga.lib.oh.us:210 INNOPAC - There may be other Cuyahoga Counties in the USA, but 95% positive this is the Cuyahoga that is now using Koha via ByWater Solutions OCEAN STATE LIBRARIES (RI) catalog.oslri.net:210 INNOPAC - Same as Cuyahoga **In general, would there be catalogs that use Koha willing to share their connection information and then remove the connections that no longer are valid? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 38577] New: Typo: Circulation preferences - "how you’d like the log of checked in items displays"
by bugzilla-daemon＠bugs.koha-community.org 30 Jul '25

30 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38577 Bug ID: 38577 Summary: Typo: Circulation preferences - "how you’d like the log of checked in items displays" Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: trivial 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 In the Circulation preferences chapter, under ShowAllCheckins (https://koha-community.org/manual/latest/en/html/circulationpreferences.htm…) "choose how you’d like the log of checked in items displays" displays -> to display ?? Not 100% sure. Maybe a native English speaker could do this one. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[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 38696] New: Access control - limit content and customisations on patron category
by bugzilla-daemon＠bugs.koha-community.org 30 Jul '25

30 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38696 Bug ID: 38696 Summary: Access control - limit content and customisations on patron category Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org So far we can limit content (i.e. item types) and customisations (i.e additional contents like HTML customisations and CMS pages) on library. It would be great if we could also limit on patron category. -- You are receiving this mail because: You are watching all bug changes.

1 2