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

[Bug 29115] New: Placing a club hold is not showing warnings when unable to place a hold
by bugzilla-daemon＠bugs.koha-community.org 02 Feb '22

02 Feb '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29115 Bug ID: 29115 Summary: Placing a club hold is not showing warnings when unable to place a hold Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: joonas.kylmala(a)iki.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com The code that is supposed to show warnings if someone in a club cannot reserve the item when placing a club hold is broken and not showing the warnings. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 24993] New: koha-sip --restart is too fast, doesn't always start sip
by bugzilla-daemon＠bugs.koha-community.org 02 Feb '22

02 Feb '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24993 Bug ID: 24993 Summary: koha-sip --restart is too fast, doesn't always start sip Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: wizzyrea(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com Sometimes doing koha-sip --restart inst happens too fast and start sip doesn't start it. A pause in there to let SIP catch up would probably fix it. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 33

[Bug 29255] New: Built-in offline circulation broken with SQL error
by bugzilla-daemon＠bugs.koha-community.org 01 Feb '22

01 Feb '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29255 Bug ID: 29255 Summary: Built-in offline circulation broken with SQL error Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: major Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Testing the built-in offline circulation system in a browser which still supports applicationCache, I ran into this error: DBD::mysql::st execute failed: Column 'branchcode' in field list is ambiguous at /kohadevbox/koha/offline_circ/download.pl line 84 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 22

[Bug 29424] New: Replace the table on 'HTML customisations' administration with a visual alternative.
by bugzilla-daemon＠bugs.koha-community.org 01 Feb '22

01 Feb '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29424 Bug ID: 29424 Summary: Replace the table on 'HTML customisations' administration with a visual alternative. Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org There are a fixed set of 'Blocks' available for HTML Customisations.. I propose that instead of a table, we have a more visual representation of where these blocks will appear once content is added to them. Something more akin to the image we have in the Manual that is used to display where the blocks reside: https://koha-community.org/manual/21.05/en/html/tools.html?highlight=custom… But with the "Green blocks" being clickable to enter the editing process. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 28698] New: News for all displays in all locations
by bugzilla-daemon＠bugs.koha-community.org 31 Jan '22

31 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28698 Bug ID: 28698 Summary: News for all displays in all locations Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Some news are used for custom text with a specific language, for example "opacheader". The bug is that in these locations, news for all (staff and opac) are displayed. This is because GetNewsToDisplay uses SQL : opac_news.lang = '' OR opac_news.lang = ? -- You are receiving this mail because: You are watching all bug changes.

1 24

[Bug 29437] New: 500 error when performing a catalog search for an ISBN13 with no valid ISBN10
by bugzilla-daemon＠bugs.koha-community.org 31 Jan '22

31 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29437 Bug ID: 29437 Summary: 500 error when performing a catalog search for an ISBN13 with no valid ISBN10 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When performing a cataloging search we take the query and test to see if it is a valid isbn: If not, we perform a SQL search for the term as author or title If so, we pass it to BreedingSearch as an ISBN - we then normailize it to ISBN 10 - then perform aSQL search for ISBN In the ISBN case, if it cannot be converted to a 10 digit ISBN we nullify the term - the SQL then has no where statement and fails in plack-error.log: C4::Breeding::BreedingSearch(): DBI Exception: DBD::mysql::st execute failed: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near '' at line 5 at /kohadevbox/koha/cataloguing/addbooks.pl line 117 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 35

[Bug 29319] New: Errors when doing a cataloging search which starts with a number + letter
by bugzilla-daemon＠bugs.koha-community.org 31 Jan '22

31 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29319 Bug ID: 29319 Summary: Errors when doing a cataloging search which starts with a number + letter Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl To recreate: Go to addbooks.pl and try a catalog search that starts with a number like 3rd degree, 7th heaven, or 6th target. The searches will result in an ugly error page and the following in the error logs: C4::Breeding::BreedingSearch(): DBI Exception: DBD::mysql::st execute failed: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near '' at line 5 at /kohadevbox/koha/cataloguing/addbooks.pl line 123 at /usr/share/perl5/DBIx/Class/Exception.pm line 77 DBIx::Class::Exception::throw('DBIx::Class::Exception', 'DBI Exception: DBD::mysql::st execute failed: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near \'\' at line 5', 0) called at /usr/share/perl5/DBIx/Class/Schema.pm line 1118 DBIx::Class::Schema::throw_exception('Koha::Schema=HASH(0x560206b40608)', 'DBI Exception: DBD::mysql::st execute failed: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near \'\' at line 5') called at /usr/share/perl5/DBIx/Class/Storage.pm line 113 DBIx::Class::Storage::throw_exception('DBIx::Class::Storage::DBI::mysql=HASH(0x560206d0e768)', 'DBI Exception: DBD::mysql::st execute failed: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near \'\' at line 5') called at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1501 DBIx::Class::Storage::DBI::__ANON__('DBD::mysql::st execute failed: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near \'\' at line 5', 'DBI::st=HASH(0x56020b84bbe8)', undef) called at /kohadevbox/koha/C4/Breeding.pm line 99 C4::Breeding::BreedingSearch(undef, '7th heaven') called at /kohadevbox/koha/cataloguing/addbooks.pl line 123 eval {...} at /kohadevbox/koha/cataloguing/addbooks.pl line 2 Note: If I search for something like '33rd Heaven', 77th target, I get no error -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 25

[Bug 28472] New: UpdateItemLocationOnCheckin not updating items where location is null
by bugzilla-daemon＠bugs.koha-community.org 31 Jan '22

31 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28472 Bug ID: 28472 Summary: UpdateItemLocationOnCheckin not updating items where location is null Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com UpdateItemLocationOnCheckin can be set to update ALL items at checkin. But that ALL is excluding items where location is null. To recreate: - have a location CART - in UpdateItemLocationOnCheckin, enter "_ALL_: CART" - find an item with a shelving location, check it in, confirm it changes to CART - find an item with a NULL shelving location, check it in, confirm it doesn't go to CART -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 33

[Bug 29284] New: Koha dies when an analytics search fails in Elasticsearch
by bugzilla-daemon＠bugs.koha-community.org 31 Jan '22

31 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29284 Bug ID: 29284 Summary: Koha dies when an analytics search fails in Elasticsearch Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com Bug 28316 added some escaping of reserved ES characters, bug 28484 used the escaping on detail pages, however, it seems there may still be combinations that break the search. We should prevent a failure when loading these records To recreate: 1 - Add a title to catalog, with 245a: Digger does it all (not really!) 2 - Set searchEngine preference to: Elasticsearch 3 - The record does not load -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 22

[Bug 27488] New: Rename system preference suggestion to OPACPurchaseSuggestions
by bugzilla-daemon＠bugs.koha-community.org 28 Jan '22

28 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27488 Bug ID: 27488 Summary: Rename system preference suggestion to OPACPurchaseSuggestions 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: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org find all of the places in the code that refer to the 'suggestion' system preference and rename them to 'OPACPurchaseSuggestions' write an atomic update to rename the suggestion system preference to OPACPurchaseSuggestions in the preferences table in the database rename the suggestion syspref in sysprefs.sql refer to bug 10328 for an example -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4