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

[Bug 37867] New: (Bug 36794 follow-up) Warning "Use of uninitialized value in substitution..." while creating a new bibliographical record
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37867 Bug ID: 37867 Summary: (Bug 36794 follow-up) Warning "Use of uninitialized value in substitution..." while creating a new bibliographical record Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Cataloging Assignee: januszop(a)gmail.com Reporter: januszop(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl, tomascohen(a)gmail.com Depends on: 36794 After applying the patch 36794 a warning: Use of uninitialized value in substitution (s///) at /kohadevbox/koha/Koha/UI/Form/Builder/Biblio.pm line 53. is being generated when creating a new bibliographical record. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36794 [Bug 36794] Illegitimate modification of biblionumber subfield content (999 $c) -- You are receiving this mail because: You are watching all bug changes.

1 8

[Bug 36794] New: Illegitimate modification of biblionumber subfield content (999 $c)
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36794 Bug ID: 36794 Summary: Illegitimate modification of biblionumber subfield content (999 $c) Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Cataloging Assignee: januszop(a)gmail.com Reporter: januszop(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl It happens that librarians, by mistake, open a biblio editor putting in the URL, by hand, the biblionumber prefixed with a blank (e.g. .../addbiblio.pl?biblionumber= 123 -- mind the space before 123). In such a case the editor opens with the right biblio record (i.e. 123) but, after saving the record, the content of the biblionumber MARC field (999 $c for a standard MARC 21 installation) results modified and contains additional initial blanks. Moreover, while using ES and making a search for the record (with title, author etc.) we get two records on the result list (instead of one). This is because in the addbiblio.pl script $biblionumber is taken (and continuously used) directly from CGI parameter, without any validation and/or correction. -- You are receiving this mail because: You are watching all bug changes.

1 25

[Bug 36799] New: Illegitimate modification of MARC authid field content (001)
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36799 Bug ID: 36799 Summary: Illegitimate modification of MARC authid field content (001) Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: MARC Authority data support Assignee: januszop(a)gmail.com Reporter: januszop(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org It happens that librarians to save time open an authority editor by putting in the URL, by hand, the authid prefixed, by mistake, with a blank (e.g. .../authorities.pl?authid= 100 -- mind the space before 100). In such a case the editor opens with the right auth record (i.e. 100) but, after saving the record, the content of the authid MARC field (001 for a standard MARC 21 installation) results modified and contains additional initial blanks. Moreover, if the heading (1XX field) was modified in the authority record during such an edit, the changes will not propagate to the linked bibliographic records. And won't in the future. This is because in the authorities.pl script $authid is taken (and continuously used) directly from CGI parameter, without any validation and/or correction (line 540 in the current main branch). -- You are receiving this mail because: You are watching all bug changes.

1 19

[Bug 33849] New: Duplicate patron warning resets borrowers branch if different than logged in user's branch
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33849 Bug ID: 33849 Summary: Duplicate patron warning resets borrowers branch if different than logged in user's branch Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: lisette.scheer(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When entering a new patron, if the patron's home library is not the same as the logged-in library of the user + the patron is flagged as a possible duplicate, the patron's home library reverts to the logged in user's library. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 34041] New: z3950 responder additional options not coming through properly
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34041 Bug ID: 34041 Summary: z3950 responder additional options not coming through properly Change sponsored?: --- Product: Koha Version: master 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: wizzyrea(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl The z3950 responder default configuration has responder options, but the start script is looking for them in the <config> node, which isn't in the config, so it never finds them if required. Probably we need to fix that, one way or another. :) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 20

[Bug 36676] New: SIP2 drops connection when using unknown patron id in fee paid message
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36676 Bug ID: 36676 Summary: SIP2 drops connection when using unknown patron id in fee paid message Change sponsored?: --- Product: Koha Version: 23.11 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: bibliothek(a)th-wildau.de QA Contact: testopia(a)bugs.koha-community.org When sending a fee paid message to SIP2 with an unknown patron id it will respond with an empty response followed by dropping the connection to a client. to test on ktd (23.11): a) perl /usr/share/koha/bin/sip_cli_emulator.pl -a 127.0.0.1 -p 6001 -su term1 -sp term1 -l CPL --patron 2352900100046 -m fee_paid --fee-type FT --fee-amount 0.01 The reason for this is in C4/SIP/ILS.pm pay_fee as it calls return $trans; if no patron is found. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 24

[Bug 36534] New: Batch operations when using limit in report
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36534 Bug ID: 36534 Summary: Batch operations when using limit in report Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: mikko.liimatainen(a)turku.fi QA Contact: testopia(a)bugs.koha-community.org When running a report with defined limit larger than 20, batch operations reads "Batch operations with 20 visible records" even though more records are visible. However when doing a batch operation it is done to all visible records. To reproduce: 1. Create a report of items with a limit of over 20 2. Run report 3. See that number of results shown exceeds 20 4. Dropdown reads "Batch operations with 20 visible records" 5. Start Batch item modification 6. Batch modification opens with all visible records -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 36554] New: Document languages from field 041 should be present in 'ln' search field and Languages facet (MARC 21)
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36554 Bug ID: 36554 Summary: Document languages from field 041 should be present in 'ln' search field and Languages facet (MARC 21) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: januszop(a)gmail.com In Elasticsearch, the field 041 (subfields: a, d, e, i, j) is not indexed with 'ln' search field. As a result records cannot be found when searching with languages present in 041 (but only with the one from 008/35-37), and the languages are also missing from the facet. Subfields content (only relevant subfields): $a - Language code of text/sound track or separate title $d - Language code of sung or spoken text $e - Language code of librettos $i - Language code of intertitles $j - Language code of subtitles All these subfields are repeatable. The most important is of course 041 $a but the rest could be also of interest. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 36390] New: Two minor OPAC CSS fixes
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36390 Bug ID: 36390 Summary: Two minor OPAC CSS fixes Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org 1. Some Font Awesome icons are not getting styled correctly because we forgot to update the class list to include .fa-solid. 2. The floating toolbar on pages like catalog search results has an unwanted top margin. -- You are receiving this mail because: You are watching all bug changes.

1 13

[Bug 36567] New: Datetime warning in t/db_dependent/Circulation.t and t/db_dependent/Circulation/dateexpiry.t
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36567 Bug ID: 36567 Summary: Datetime warning in t/db_dependent/Circulation.t and t/db_dependent/Circulation/dateexpiry.t Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: emmi.takkinen(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org Running t/db_dependent/Circulation.t and t/db_dependent/Circulation/dateexpiry.t causes following warning: >You are creating a DateTime object with a far future year (9999) and a time >zone (Europe/Helsinki). If the time zone you specified has future DST changes >this will be very slow. at ../Koha/C4/Circulation.pm line 1614. Datetime modules pod states (https://metacpan.org/pod/DateTime) >Currently, constructors will warn if you try to create a far future DateTime >(year >= 5000) with any time zone besides floating or UTC. This can be very >slow if the time zone has future DST transitions that need to be calculated. >If the date is sufficiently far in the future this can be really slow >(minutes). -- You are receiving this mail because: You are watching all bug changes.

1 16