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

[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 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 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 28502] New: Changing patron category from child to adult doesn't delete non patron guarantor data.
by bugzilla-daemon＠bugs.koha-community.org 26 Jun '26

26 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28502 Bug ID: 28502 Summary: Changing patron category from child to adult doesn't delete non patron guarantor data. Change sponsored?: --- Product: Koha Version: 20.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: didier.gautheron(a)biblibre.com Reporter: didier.gautheron(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com But guarantor name and relationship fields aren't displayed anymore and librarian can't delete them manually. -- You are receiving this mail because: You are watching all bug changes.

1 8

[Bug 38185] New: DT - replace dom with layout
by bugzilla-daemon＠bugs.koha-community.org 26 Jun '26

26 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38185 Bug ID: 38185 Summary: DT - replace dom with layout Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Depends on: 36640 https://datatables.net/upgrade/2#dom-property """ dom is still available in DataTables 2 (likely it will be dropped in v3 whenever that happens!), but the default CSS for DataTables has been updated for layout and does not include styling for dom. If you need to continue using dom, you will likely need to add some CSS to position the elements as you need. However, you are strongly encouraged to update to using layout. """ Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36640 [Bug 36640] Upgrade DataTables from 1.13.6 to 2.x -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 67

[Bug 36444] New: Place Holds for Patrons Purchase Suggestion when not using Acquisitions Process
by bugzilla-daemon＠bugs.koha-community.org 26 Jun '26

26 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36444 Bug ID: 36444 Summary: Place Holds for Patrons Purchase Suggestion when not using Acquisitions Process Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com With the passing of the bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27595, holds can now be placed on purchase suggestions, however, this only applies to purchase suggestions that are ordered through Acquisitions. It would be nice if this process could work without using the Acquisitions Module. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 19358] New: Purchase suggestions - enhancements to linking to orders
by bugzilla-daemon＠bugs.koha-community.org 26 Jun '26

26 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19358 Bug ID: 19358 Summary: Purchase suggestions - enhancements to linking to orders Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org 1 - Build a matching tool between purchase suggestions and staged files for Koha using standard fields 1a - Allow for defining fields to match (ISBN -> 020 ) etc. 1b - Add the biblionumber to the request 2 - Build a search tool for suggestions to allow linking multiple suggestions to a staged file 2a - This will be a popup window and allow for multiple suggestions selected to link to the biblio 3 - When an item is received on the linked biblio the receiving process will check for linked suggestions and notify the user(s) using a defined template -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 37

[Bug 27190] New: Debug REST API tests
by bugzilla-daemon＠bugs.koha-community.org 26 Jun '26

26 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27190 Bug ID: 27190 Summary: Debug REST API tests Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org It can be tricky to debug REST API tests. You can get a "received 500 when 200 expected", but you don't have the error. There is one manual way to do it: $t->put_ok($url)->status_is(200)->json_is($expected_json)->or( sub { warn $t->tx->res->to_string }); But could we provide a generic way to add a diag in case Test::Mojo fails? -- You are receiving this mail because: You are watching all bug changes.

1 6

[Bug 37815] New: Protected flag permissions should be honoured in the REST API
by bugzilla-daemon＠bugs.koha-community.org 26 Jun '26

26 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37815 Bug ID: 37815 Summary: Protected flag permissions should be honoured in the REST API Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: jake.deery(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com (follow-up from bug 36085) We now restrict access to the protected flag in the GUI. This should also be replicated out to the REST API. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 28357] New: E-mail Verification
by bugzilla-daemon＠bugs.koha-community.org 26 Jun '26

26 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28357 Bug ID: 28357 Summary: E-mail Verification Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Dead e-mails are a pain to deal with. It would be great if e-mail notifications were verified, regardless of registering online or in person. If an e-mail address is entered by staff, Koha should have a flag to indicate if the address has been verified. When an account is saved or updated, it should check if an e-mail address has been entered. If so, if it has not been verified, it should send a verification e-mail to the address. When the patron receives it, they should have to click something or login to complete the verification. The address is marked in their account as verified. If the address is changed at all, they have to re-verify. Staff who receive notice that the e-mail has problems (dead, full, etc) should have a flag they can set on the account to mark the address as bad, and the reason why. The patron would then have to supply a new e-mail address and verify again. While the account is flagged with a bad e-mail, notifications to that address should be turned off. If they have another form of notification, Koha could send them a notification that the e-mail address they supplied is no longer working, and needs to be corrected. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5