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

[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

[Bug 36122] New: NEW_SUGGESTION is sent for every modification to the suggestion
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36122 Bug ID: 36122 Summary: NEW_SUGGESTION is sent for every modification to the suggestion Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org If EmailPurchaseSuggestions is enabled, a new NEW_SUGGESTION notice is sent to the staff every time a modification is made to the suggestion. Create the suggestion --> NEW_SUGGESTION is sent to staff Accept the suggestion --> ACCEPTED is sent to patron; NEW_SUGGESTION is sent to staff Order the suggestion --> ORDERED is sent to patron; NEW_SUGGESTION is sent to staff To recreate: 1. Enable EmailPurchaseSuggestions 2. Create a suggestion from the OPAC 2.1. Go to the OPAC and log in as a patron 2.2. Go to Your account > Purchase suggestions 2.3. Click New purchase suggestion 2.4. Enter a title 2.5. Click Submit your suggestion 3. Check the message_queue, there should be one NEW_SUGGESTION message sent to whichever address you chose in EmailPurchaseSuggestions (in a fresh db, there should be 1 entry in message_queue) 4. Update the suggestion to accepted 4.1. In the staff interface, go to Acquisitions > Suggestions 4.2. In the suggestions list, check the box next to the suggestion 4.3. At the bottom of the screen, choose Mark selected as: Accepted 4.4. Click Submit 5. Check the message_queue again, there should be one ACCEPTED message sent to the patron and a new NEW_SUGGESTION message sent to whichever address you chose in EmailPurchaseSuggestions (in a fresh db, there should now be 3 entries in message_queue) 6. Order the suggestion 3.1. Go to Acquisitions 3.2. Search for a vendor 3.3. Click New > Basket 3.4. Enter a basket name (Optional: for testing I like to change Create items when: cataloging the record) 3.5. Click Save 3.6. Click Add to basket 3.7. Click From a suggestion 3.8. Click Order next to the suggestion 3.9. Enter order details 3.10. Click Save 3.11. Click Close basket 3.12. Click Yes, close 7. Check the message_queue again, there should be one ORDERED message sent to the patron and a new NEW_SUGGESTION message sent to whichever address you chose in EmailPurchaseSuggestions (in a fresh db, there should now be 5 entries in message_queue) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 48

[Bug 36295] New: Space out content blocks in Batch record modification
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36295 Bug ID: 36295 Summary: Space out content blocks in Batch record modification Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org This is very minor, but I figure I'd report it anyway... When using the batch record modification tool, there is no space between the "Record type" content block and the tabbed "Source of records" block. To recreate: 1. Create a MARC modification template 1.1. Go to Cataloging > MARC modification templates > New template 1.2. Give the template a name (for example, "Hide from OPAC") 1.3. Click Submit 1.4. Click New action 1.5. Add a new action (for example, Update existing or add new field(s) 942 n with value 1) 1.6. Click Add action 2. Go to Cataloging > Batch record modification --> Note that there is no space between the white "Record type" block and the block underneath with the tabs for the record source -- You are receiving this mail because: You are watching all bug changes.

1 22

[Bug 33205] New: (Bug 28268 follow-up) Method call inside quotes
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33205 Bug ID: 33205 Summary: (Bug 28268 follow-up) Method call inside quotes 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 CC: ere.maijala(a)helsinki.fi Bug 28268, in Koha::MetadataRecord::Authority::get_all_authorities_iterator, introduced a warning: warn "Something went wrong reading record for authority $row->authid: $@\n"; But a method cannot be called from within quotes in Perl - extrapolation does not work for functions/methods. So, if something really goes wrong, this line of code produces a warning like: Something went wrong reading record for authority Koha::Schema::Result::AuthHeader=HASH(0x55cf7e0d0958)->authid: Empty String at /usr/share/perl5/MARC/File/XML.pm line 450. which is not very informative -- authid is missing. Proposal: $row->authid should be placed outside of the quotes. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 36552] New: Update record 'date entered on file' when duplicating a record
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36552 Bug ID: 36552 Summary: Update record 'date entered on file' when duplicating a record Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P3 Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: januszop(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl The 'date entered on file' (MARC21: 008/0-5, UNIMARC: 100a/0=7) of a record created by duplication of an existing record should be set to the current date instead of having the value of the original record. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 21