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

[Bug 41406] New: Error when accessing MARC structure for a new authority type
by bugzilla-daemon＠bugs.koha-community.org 08 Dec '25

08 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41406 Bug ID: 41406 Summary: Error when accessing MARC structure for a new authority type Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: david(a)davidnind.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl I get this error after creating a new authority type and going to Actions > MARC structure (for a MARC21 instance): CGI::Compile::ROOT::kohadevbox_koha_admin_auth_tag_structure_2epl::auth_tag_structure_2epl(): DBI Exception: DBD::mysql::st execute failed: 'koha_kohadev.auth_types.authtypetext' isn't in GROUP BY at /usr/share/perl5/CGI/Emulate/PSGI.pm line 30 at /usr/share/perl5/DBIx/Class/Exception.pm line 77 Steps to reproduce: 1. Go to Koha administration > Catalog > Authority types 2. Create a new authority type: - + New authority type - Authority type: anything, for example: MYAUTHTYPE - Description: anything, for example: A new authority type - Summary: no text required - Authority field to copy: 100 (same as used by Personal Name authority type) 3. For the new authority framework, select Actions > MARC structure 4. You get the error above 5. Note that I can export an existing authority type and then import it into the new authority type, then Actions > MARC structure works -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 20338] New: Preference noissuescharge should not be considered 5 when it is actually 0
by bugzilla-daemon＠bugs.koha-community.org 08 Dec '25

08 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20338 Bug ID: 20338 Summary: Preference noissuescharge should not be considered 5 when it is actually 0 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: josef.moravec(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When the noissuescharge is set to 0, then limit 5 is used, see FIXME comment in circ/circulation.pl after bug 19933 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 25219] New: Include note in fines-related system preferences which can be disabled by leaving them blank
by bugzilla-daemon＠bugs.koha-community.org 08 Dec '25

08 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25219 Bug ID: 25219 Summary: Include note in fines-related system preferences which can be disabled by leaving them blank Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration 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 The syspref OPACFineNoRenewals includes the note "(leave blank to disable)." The sysprefs maxoutstanding, noissuescharge, NoIssuesChargeGuarantees, and MaxFine can all be disabled by leaving them blank, as well. It'd be helpful to include that same "(leave blank to disable)" message to make it clear. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 38704] New: noissuescharge null value should disable
by bugzilla-daemon＠bugs.koha-community.org 08 Dec '25

08 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38704 Bug ID: 38704 Summary: noissuescharge null value should disable Change sponsored?: --- Product: Koha Version: 23.11 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: holly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Until 23.11 a null value/blank for system preference noissuescharge effectively disabled it. Beginning in 23.11, null value functions like 0, blocking patrons with any amount in fines and fees from checkout. Libraries that do not want to have patrons blocked for outstanding fines are putting in an arbitrary high number as a workaround. I can't find anything in bugzilla or release notes indicating this as an intentional change in behavior. See bug 25219 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 38950] New: Patron Attribute Fields are copied when account is Duplicated
by bugzilla-daemon＠bugs.koha-community.org 08 Dec '25

08 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38950 Bug ID: 38950 Summary: Patron Attribute Fields are copied when account is Duplicated Change sponsored?: --- Product: Koha Version: 24.05 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: rcoert(a)arlingtonva.us QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Created attachment 176939 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=176939&action=e… Patron Attribute Flags Set to Yes We've noticed that any patron Additional attributes and identifiers that are set to "YES" are copied over when we Duplicate a patron account (see attached). Steps to recreate: Open existing borrower account Set Additional attributes and identifiers flags to "YES" (save and close) Click Duplicate Review Additional attributes and identifiers on duplicated account We would like to see this behavior not occur, as attribute flags are an individual setting and specific to each patron. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 37444] New: Can't filter Holds to pull by Pickup Location
by bugzilla-daemon＠bugs.koha-community.org 08 Dec '25

08 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37444 Bug ID: 37444 Summary: Can't filter Holds to pull by Pickup Location 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: stalkernoid(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 18

[Bug 30800] New: Ability to view, modify, and delete profiles for staging MARC records for import
by bugzilla-daemon＠bugs.koha-community.org 08 Dec '25

08 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30800 Bug ID: 30800 Summary: Ability to view, modify, and delete profiles for staging MARC records for import Change sponsored?: --- Product: Koha Version: 21.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Bibliographic record staging/import Assignee: koha-bugs(a)lists.koha-community.org Reporter: sbrown(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org It would be useful to have a place to view/edit all profiles that a library has created for use while staging MARC records for import in one place - maybe similar to 'Manage MARC modification templates'. It could include each profile's settings and the ability to delete individual/multiple at a time, and if possible, the ability to add new, edit existing, and/or duplicate to create new. But at a minimum, being able to see what exists and delete from there rather than the 'Stage MARC records for import' screen would be helpful. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 38901] New: Visualization of duplicated barcodes during import
by bugzilla-daemon＠bugs.koha-community.org 08 Dec '25

08 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38901 Bug ID: 38901 Summary: Visualization of duplicated barcodes during import Change sponsored?: --- Product: Koha Version: 24.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Bibliographic record staging/import Assignee: koha-bugs(a)lists.koha-community.org Reporter: verolencinas(a)yahoo.com.ar QA Contact: testopia(a)bugs.koha-community.org If you import MARC bibliographic files, duplicates barcodes will result in failure to import this particular item while the record will still be imported. The general information is shown in the job detail report ("Number of items ignored"), but it is not possible to identify the specific items with this problem. It would be beneficial to show this issue in the detailed view ("Manage imported batch") to identify the problematic items. This could be applied to other import problems for items. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 41401] New: Translating Custom slips adds same amount of options to the Print dropdown in patron's details
by bugzilla-daemon＠bugs.koha-community.org 08 Dec '25

08 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41401 Bug ID: 41401 Summary: Translating Custom slips adds same amount of options to the Print dropdown in patron's details Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: anneli.osterman(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org Created attachment 190287 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=190287&action=e… Custom slip with two languages When you add a custom slip and there are several languages installed and translating notices (TranslateNotices system preference) is allowed there will be as many options as added languages in the Print dropdown menu in patron's details. All of those options print the slip in the the language that has been selected as patron's Preferred language for notices. So, if you have three languages plus default you will get four options that all look the same (name comes from the Name of the notice) and prints the same content. How to reproduce: 1. Make sure you have at least to languages added to Koha. 2. Select in StaffInterfaceLanguages systempreferences at least two of those languages 3. Choose "Allow" to TranslateNotices systempreference 4. Go to Tools - Notices and slips - New notice - Patrons (custom slip) 5. Add code (TEST) and Name (Testing languages) 6. Add (different) content to at least two languages 7. Go to random patron's details and modify to select one of the selected languages as Preferred language for notices. Save. 8. Select Print from the toolbar and notice that there are at least two custom slips with the same name 9. Try to print both/all of them and notice that all of them prints the content in the language that patron has preferred. See the screenshot attached. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 11999] Add two checks in CanBookBeReserved and CanItemBeReserved
by bugzilla-daemon＠bugs.koha-community.org 07 Dec '25

07 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11999 --- Comment #144 from David Nind <david(a)davidnind.com> --- To clarify: 1. prove t/db_dependent/Reserves.t fails 2. prove t/db_dependent/Holds.t passes prove t/db_dependent/Reserves.t t/db_dependent/Reserves.t .. 68/71 # Looks like you planned 71 tests but ran 72. t/db_dependent/Reserves.t .. Dubious, test returned 255 (wstat 65280, 0xff00) All 71 subtests passed Test Summary Report ------------------- t/db_dependent/Reserves.t (Wstat: 65280 (exited 255) Tests: 72 Failed: 1) Failed test: 72 Non-zero exit status: 255 Parse errors: Bad plan. You planned 71 tests but ran 72. Files=1, Tests=72, 8 wallclock secs ( 0.03 usr 0.01 sys + 5.49 cusr 1.97 csys = 7.50 CPU) Result: FAIL kohadev-koha@kohadevbox:koha(bz11999)$ prove t/db_dependent/Holds.t t/db_dependent/Holds.t .. ok All tests successful. Files=1, Tests=74, 6 wallclock secs ( 0.03 usr 0.00 sys + 4.31 cusr 1.48 csys = 5.82 CPU) Result: PASS -- You are receiving this mail because: You are watching all bug changes.

1 0