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

[Bug 30904] New: (bug 24387 follow-up) Modifying library in news (additional contents) causes inconsistencies
by bugzilla-daemon＠bugs.koha-community.org 14 Oct '22

14 Oct '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30904 Bug ID: 30904 Summary: (bug 24387 follow-up) Modifying library in news (additional contents) causes inconsistencies Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: januszop(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Modifying an existing element of additional content (News) by changing the library causes a duplication of the entry on the Additional contents (News) list. A subsequent attempt of deleting one of the entries results in deleting both of them. This is due to the fact that after the unwanted duplication all the entries share the same additional_contents.code. A patch will follow. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 23

[Bug 30974] New: Job size not correct for indexing jobs
by bugzilla-daemon＠bugs.koha-community.org 14 Oct '22

14 Oct '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30974 Bug ID: 30974 Summary: Job size not correct for indexing jobs Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart+koha(a)gmail.com Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 22417 job's size is the number of records to index, but when finished the progress is always set to 1. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22417 [Bug 22417] Add a task queue -- You are receiving this mail because: You are watching all bug changes.

1 11

[Bug 30677] New: Unknown column 'biblioitem.title' in 'where clause' 500 error in API /api/v1/acquisitions/orders
by bugzilla-daemon＠bugs.koha-community.org 14 Oct '22

14 Oct '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30677 Bug ID: 30677 Summary: Unknown column 'biblioitem.title' in 'where clause' 500 error in API /api/v1/acquisitions/orders Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: nugged(a)gmail.com CC: tomascohen(a)gmail.com Depends on: 30165 The exception: [ERROR] GET /api/v1/acquisitions/orders: unhandled exception (DBIx::Class::Exception)<<DBIx::Class::Storage::DBI::_dbh_execute(): DBI Exception: DBD::mysql::st execute failed: Unknown column 'biblioitem.title' in 'where clause' at /usr/share/perl5/Data/Page.pm line 49 Because here is the experimental dump of what sub table_name_fixer replaces: in: 'q' => '{"-and":[{"basket.vendor_id":2},[[{"basket.name":{"like":"%f%"}}],[{"basket.basket_group.name":{"like":"%f%"}}],[{"me.order_id":{"like":"%f%"}}],[{"biblio.title":{"like":"%f%"}},{"biblio.author":{"like":"%f%"}},{"biblio.isbn":{"like":"%f%"}},{"biblio.publisher":{"like":"%f%"}},{"me.internal_note":{"like":"%f%"}},{"me.vendor_note":{"like":"%f%"}}],[{"me.replacement_price":{"like":"%f%"}}],[{"me.quantity":{"like":"%f%"}}],[{"me.ecost":{"like":"%f%"}}],[{"fund.name":{"like":"%f%"}}]]]}' }; out: 'q' => '{"-and":[{"basket.vendor_id":2},[[{"basket.name":{"like":"%f%"}}],[{"basket.basket_group.name":{"like":"%f%"}}],[{"me.order_id":{"like":"%f%"}}],[{"biblio.biblioitem.title":{"like":"%f%"}},{"biblio.biblioitem.author":{"like":"%f%"}},{"biblio.biblioitem.isbn":{"like":"%f%"}},{"biblio.biblioitem.publisher":{"like":"%f%"}},{"me.internal_note":{"like":"%f%"}},{"me.vendor_note":{"like":"%f%"}}],[{"me.replacement_price":{"like":"%f%"}}],[{"me.quantity":{"like":"%f%"}}],[{"me.ecost":{"like":"%f%"}}],[{"fund.name":{"like":"%f%"}}]]]}' }; That because this: $q =~ s|biblio\.|biblio\.biblioitem\.|g if $q =~ m/.*(isbn|ean|publisher).*/; should be with lookahead to exclude false matches: $q =~ s{biblio\.(?=isbn|ean|publisher)}{biblio\.biblioitem\.}g; Making a fix. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30165 [Bug 30165] Several q parameters break the filters -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 42

[Bug 30848] New: Introduce Koha::Filter::AuthorizedValues
by bugzilla-daemon＠bugs.koha-community.org 14 Oct '22

14 Oct '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30848 Bug ID: 30848 Summary: Introduce Koha::Filter::AuthorizedValues Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org I think we should introduce a Koha::Filter for replacing AV codes with AV values in the MARC::Record.. we already do this using C4::XSLT::transformMARCXML4XSLT but I believe a RecordProcessor makes more sense than to hide the function away in the defunct XSLT module. We can then use this anywhere we have a RecordProcessor instantiated and get the goodness of filtered MARC::Records. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 91

[Bug 31246] New: <span> displayed in 'Additional fields' section
by bugzilla-daemon＠bugs.koha-community.org 14 Oct '22

14 Oct '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31246 Bug ID: 31246 Summary: <span> displayed in 'Additional fields' section Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Introduced by bug 30733. -- You are receiving this mail because: You are watching all bug changes.

1 13

[Bug 31247] New: Staff interface 2FA blocks logging into the OPAC
by bugzilla-daemon＠bugs.koha-community.org 14 Oct '22

14 Oct '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31247 Bug ID: 31247 Summary: Staff interface 2FA blocks logging into the OPAC Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org I noticed when I turned on the 2FA for my staff account, I'm no longer able to log into the OPAC with that same account. I usually use the same account for both, so I find this a major drawback in using 2FA. To test: 1) With 2FA turned off, log into the staff interface with your staff account --> login is normal 2) With 2FA turned off, log into the OPAC with the same account --> login is normal 3) Turn on 2FA 3.1) In System preferences, enable TwoFactorAuthentication 3.2) Go to 'My account' (click your username in the top right and choose 'My account) 3.3) Click More > Manage two-factor authentication 3.4) Click Enable two-factor authentication 3.5) With an authenticator app (I used FreeOTP) scan the QR code 3.6) Enter the PIN provided by the app in the PIN code field 3.7) Click Register with two-factor app 4) Log out of the staff interface 5) Log into the staff interface --> Username, password and two-factor code is needed 6) Log out of the OPAC 7) Log into the OPAC (I used the login box on the right) --> It cycles back to the login page, you can never log in 8) In the staff interface, disable 2FA 8.1) In 'My account', click More > Manage two-factor authentication 8.2) Click Disable two-factor authentication 9) Log into the OPAC --> login is normal -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 21

[Bug 31274] New: OPACSuggestionAutoFill must be 1 or 0
by bugzilla-daemon＠bugs.koha-community.org 14 Oct '22

14 Oct '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31274 Bug ID: 31274 Summary: OPACSuggestionAutoFill must be 1 or 0 Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 14242 It's "yes" or "no". Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14242 [Bug 14242] Use ISBN-field to fill out purchase suggestions using Google Books API -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 30747] New: Column settings on otherholdings table in detail.tt doesnt work
by bugzilla-daemon＠bugs.koha-community.org 14 Oct '22

14 Oct '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30747 Bug ID: 30747 Summary: Column settings on otherholdings table in detail.tt doesnt work Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com If you turn on the system preference SeparateHoldings you will get a otherholdings table on detail.tt. Table settings cannot be applied to this table. The the Columns icon is not present in the top pager. The reason is because of the JS: if ( !has_images[i] ) { // remove the cover_image column table_settings.splice(1,1); } table_settings.splice(1,1) is removing the table settings that control the otherholdings table columns. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 28

[Bug 30776] New: import_webservice_batch.pl cronjob completely broken
by bugzilla-daemon＠bugs.koha-community.org 14 Oct '22

14 Oct '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30776 Bug ID: 30776 Summary: import_webservice_batch.pl cronjob completely broken Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: joonas.kylmala(a)iki.fi QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz The import_webservice_batch.pl cronjob doesn't work at all due to a missing import. > $ perl misc/cronjobs/import_webservice_batch.pl > Undefined subroutine &main::GetStagedWebserviceBatches called at misc/cronjobs/import_webservice_batch.pl line 46 Not sure if anyone uses this but this is an easy fix, we can remove the feature later if it is unused. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 10

[Bug 30714] New: Checkins from other branches spam the cataloguing log
by bugzilla-daemon＠bugs.koha-community.org 14 Oct '22

14 Oct '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30714 Bug ID: 30714 Summary: Checkins from other branches spam the cataloguing log Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When an item from another branch is checked in, the holdingbranch is updated, and this change is logged. We record the checkin in statistics, we do not need the cataloguing update logged To recreate: 1 - Enable cataloguing log 2 - Check in an item with a different holding branch 3 - Check the action logs 4 - There is a cataloguing log for the holdingbranch update -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17