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

[Bug 25603] New: Add 001 and 003 to biblio table
by bugzilla-daemon＠bugs.koha-community.org 27 Jun '26

27 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25603 Bug ID: 25603 Summary: Add 001 and 003 to biblio table Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Bibliographic data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org Koha itself does not care too much about these fields, but sometimes they are used when importing/syncing in records from external sources, and then it can be work intensive to match on WHERE ExtractValue( metadata,\'//controlfield[@tag="001"]\' ). This would be much easier if the 001 and 003 fields from the record had their own database columns we could match on. Similar to: Bug 11529 - Add subtitle, medium and part fields to biblio table -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 23

[Bug 19339] New: Enhance streaming cataloging to include Vimeo
by bugzilla-daemon＠bugs.koha-community.org 27 Jun '26

27 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19339 Bug ID: 19339 Summary: Enhance streaming cataloging to include Vimeo Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: leire(a)scanbit.net QA Contact: testopia(a)bugs.koha-community.org It will work like Youtube videos but with links of Vimeo. -- You are receiving this mail because: You are watching all bug changes.

1 41

[Bug 42931] New: move Global HTML notice styles below the notices
by bugzilla-daemon＠bugs.koha-community.org 26 Jun '26

26 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42931 Bug ID: 42931 Summary: move Global HTML notice styles below the notices Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: lisette(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: martin.renvoize(a)openfifth.co.uk Target Milestone: --- Bug 35267 moved the Global HTML notice styles above the notices, which has caused a lot of confusion with users. As they're less likely to be used per visit than the notice content, I think we should move them back below. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 35267] New: Add further CSS options for Notices
by bugzilla-daemon＠bugs.koha-community.org 26 Jun '26

26 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35267 Bug ID: 35267 Summary: Add further CSS options for Notices Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org During review of bug 33487 I made the suggestion that we should have more CSS options for our notices at the system preference level. I've also hit this when looking into bug 30287. So.. recording this here and hopefully we'll find some time to work on it. Personally.. I'd have * EmailNoticeCSS - CSS stored in the DB for email notice CSS * EmailNoticeCSSHosted - Location of CSS file for email notice CSS (to retain the old NoticeCSS option) * PrintNoticeCSS - CSS stored in the DB for print notice CSS * PrintNoticeCSSHosted - Location of the CSS file for the print notice CSS (to reatin the old SlipCSS option) SMS doesn't support HTML/CSS so no need for that transport type to have these CSS options. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 315

[Bug 42646] New: ModSuggestion: SMS status-change notices always contain email template content
by bugzilla-daemon＠bugs.koha-community.org 26 Jun '26

26 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42646 Bug ID: 42646 Summary: ModSuggestion: SMS status-change notices always contain email template content Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org In C4/Suggestions.pm, ModSuggestion() selects the transport type (email or sms) at ~line 253 and stores it in $transport, but then calls GetPreparedLetter() at ~line 256 without passing message_transport_type. GetPreparedLetter() defaults message_transport_type to 'email' when the parameter is absent (C4/Letters.pm ~line 585), so it always fetches the email template variant of the notice â even when $transport was resolved to 'sms'. The result is that any patron who legitimately receives an ACCEPTED/AVAILABLE/REJECTED/ORDERED/CHECKED notice via SMS receives the email-formatted body text rather than the SMS-specific template content. Related to: Bug 39984, Bug 42645 Test plan: 1. Configure SMSSendDriver and a patron with smsalertnumber but no email. 2. Enable FallbackToSMSIfNoEmail. 3. Create SMS-specific templates for the ACCEPTED notice code (Notices > ACCEPTED > SMS tab). 4. Submit a suggestion as that patron and accept it. 5. Check the message_queue table: the content column will contain the email template body, not the SMS template body. 6. Apply patch (add message_transport_type => $transport to the GetPreparedLetter() call in ModSuggestion). 7. Repeat: the content column now contains the SMS template body. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 41343] New: Overdue report is too intensive on systems with many overdues
by bugzilla-daemon＠bugs.koha-community.org 26 Jun '26

26 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41343 Bug ID: 41343 Summary: Overdue report is too intensive on systems with many overdues Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 20

[Bug 42726] New: Release team 26.11
by bugzilla-daemon＠bugs.koha-community.org 26 Jun '26

26 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42726 Bug ID: 42726 Summary: Release team 26.11 Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: About Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org CC: chloe.zermatten(a)openfifth.co.uk, david(a)davidnind.com, fridolin.somers(a)biblibre.com, jacob.omara(a)openfifth.co.uk, katrin.fischer(a)bsz-bw.de, lucas(a)bywatersolutions.com, m.de.rooy(a)rijksmuseum.nl, martin.renvoize(a)openfifth.co.uk, paul.derscheid(a)lmscloud.de, testopia(a)bugs.koha-community.org, wainuiwitikapark(a)catalyst.net.nz Depends on: 41317, 40022 New cycle, new release team. Let's add the new team to the about page. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40022 [Bug 40022] Release team 25.11 https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41317 [Bug 41317] Release team 26.05 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 31

[Bug 24438] New: index can fail on timeout
by bugzilla-daemon＠bugs.koha-community.org 26 Jun '26

26 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24438 Bug ID: 24438 Summary: index can fail on timeout Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com We have seen occasional timeouts when indexing elasticsearch, these cause the indexing to stop and fail. We should handle the response as the code indicates: 102 sub update_index { 103 my ($self, $biblionums, $records) = @_; 104 105 my $conf = $self->get_elasticsearch_params(); 106 my $elasticsearch = $self->get_elasticsearch(); 107 my $documents = $self->marc_records_to_documents($records); 108 my @body; 109 110 for (my $i=0; $i < scalar @$biblionums; $i++) { 111 my $id = $biblionums->[$i]; 112 my $document = $documents->[$i]; 113 push @body, { 114 index => { 115 _id => $id 116 } 117 }; 118 push @body, $document; 119 } 120 if (@body) { 121 my $response = $elasticsearch->bulk( 122 index => $conf->{index_name}, 123 type => 'data', # is just hard coded in Indexer.pm? 124 body => \@body 125 ); 126 } 127 # TODO: handle response 128 return 1; 129 } -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 9805] Lost items are un-lost if returned, but not if renewed
by bugzilla-daemon＠bugs.koha-community.org 26 Jun '26

26 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9805 mreid <mreid(a)batestech.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mreid(a)batestech.edu --- Comment #67 from mreid <mreid(a)batestech.edu> --- It would be helpful if renewals made by staff removed lost status. I get why removing lost status as result of a patron renewal presents an issue! -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 42789] New: EDI ORDRSP: Item and suggestion status not updated when order line cancelled by supplier
by bugzilla-daemon＠bugs.koha-community.org 26 Jun '26

26 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42789 Bug ID: 42789 Summary: EDI ORDRSP: Item and suggestion status not updated when order line cancelled by supplier Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org When an EDI ORDRSP message cancels an order line, Koha marks the order status to 'cancelled' but does not update the status of associated items or purchase suggestions. Items created as part of the acquisition (on-order items) retain their existing status, which can prevent holds from being placed or fulfilled. Similarly, any purchase suggestion that drove the original order is not updated to reflect that the order has been cancelled, leaving suggestions in a misleading state. Customer reports confirm that in some configurations items are being deleted on cancellation, causing holds to fail. The correct behaviour â whether to delete, update status, or transfer holds â needs to be defined and implemented consistently for the EDI cancellation code path, matching the behaviour of manual cancellation via the acquisitions UI. The processing logic is in Koha/EDI.pm, process_ordrsp() (~line 199-248). Test plan: 1. Create an order with associated on-order items and/or a linked suggestion. 2. Place a hold on one of the on-order items. 3. Receive an EDI ORDRSP cancellation for that order line and run edi_cron.pl. 4. Confirm the order line is marked cancelled. 5. Confirm on-order items are handled appropriately (status updated / holds transferred). 6. Confirm any linked suggestion is returned to a pending/unfulfilled state. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 22