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

[Bug 18908] New: Warning "Compatibility levels before 9 are deprecated"
by bugzilla-daemon＠bugs.koha-community.org 05 Jan '24

05 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18908 Bug ID: 18908 Summary: Warning "Compatibility levels before 9 are deprecated" Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Packaging Assignee: koha-bugs(a)lists.koha-community.org Reporter: mtompset(a)hotmail.com QA Contact: testopia(a)bugs.koha-community.org CC: mirko(a)abunchofthings.net The following output: dh: Compatibility levels before 9 are deprecated (level 7 in use) dh_testdir -O--fail-missing dh_auto_clean -O--fail-missing dh_auto_clean: Compatibility levels before 9 are deprecated (level 7 in use) dh_clean -O--fail-missing is given when trying to following these instructions: https://wiki.koha-community.org/wiki/Building_Debian_Packages_-_The_Easy_Way -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 11

[Bug 19616] New: Formatted Contents Note (Marc 21 505), subfield g isn' t visible in the OPAC
by bugzilla-daemon＠bugs.koha-community.org 02 Jan '24

02 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19616 Bug ID: 19616 Summary: Formatted Contents Note (Marc 21 505), subfield g isn't visible in the OPAC Change sponsored?: --- Product: Koha Version: 16.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: verolencinas(a)yahoo.com.ar QA Contact: testopia(a)bugs.koha-community.org The 505 field in Marc 21, Formatted Contents Note, includes subfield g "Miscellaneous information". According to the Marc 21 format for bibliographic data, it is used to record "volume, part, page numbering or other extent information such as dates". If you use it in Koha, this information isn't visible in the OPAC. -- You are receiving this mail because: You are watching all bug changes.

1 35

[Bug 24261] New: Google openID Authethication drops requested url
by bugzilla-daemon＠bugs.koha-community.org 02 Jan '24

02 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24261 Bug ID: 24261 Summary: Google openID Authethication drops requested url Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: mihai.bojonca(a)tcmi.edu QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org Hi everyone, i think this is a bug, we have setup access to catalog after login, we use 2 authentication methods, username and password or google openid, when a patron opens a direct link to an item and authenticates with username and password they get to the item itself however with openid they get redirected to the opac main page -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 24967] New: Allow final user to choose ordering column
by bugzilla-daemon＠bugs.koha-community.org 01 Jan '24

01 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24967 Bug ID: 24967 Summary: Allow final user to choose ordering column Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: pascale.nalon(a)mines-paristech.fr QA Contact: testopia(a)bugs.koha-community.org It would be fine, if members of staff, who have not permissions to modify a SQL requests, but only to run them, could choose the column and the way (ASC or DESC) to order the pre-builded request -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 24577] New: API schema merging breaks with older versions of JSON module
by bugzilla-daemon＠bugs.koha-community.org 31 Dec '23

31 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24577 Bug ID: 24577 Summary: API schema merging breaks with older versions of JSON module Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew.isherwood(a)ptfs-europe.com I discovered this while deploying a plugin that defines an API route. If the installation is using a version of the JSON module < 2.90, schema merging doesn't work correctly, these are the sort of errors that were being generated during validation of the merged schema: { 'path' => '/paths/~1contrib~1ill_availability_unpaywall~1ill_availability_search_unpaywall/get/parameters/0', 'message' => 'oneOf failed: oneOf failed: Properties not allowed: type. oneOf failed: (Not in enum list: header.. Expected boolean - got JSON::XS::Boolean.) (Not in enum list: formData.. Expected boolean - got JSON::XS::Boolean.) Expected boolean - got JSON::XS::Boolean. (Expected boolean - got JSON::XS::Boolean.. Not in enum list: path.) Properties not allowed: name, required, type, description, in.' } Pretty nonsensical and a nightmare to try and get to the bottom of. I was seeing this using JSON 2.61. I believe the change that was implemented in 2.90 that we're dependent on, is the top one listed here: https://metacpan.org/changes/release/MAKAMAKA/JSON-2.90 Koha is currently specifying 2.07 as the required version. I'm wondering if it is worth moving this to 2.90. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 24580] New: Allow patron_emailer or parallel structure to generate custom print notices from report output
by bugzilla-daemon＠bugs.koha-community.org 31 Dec '23

31 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24580 Bug ID: 24580 Summary: Allow patron_emailer or parallel structure to generate custom print notices from report output 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: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Bug 16149 adds the ability to combine report results with a custom notice to generate emails. Many libraries do not reliably have email addresses for their patrons and could use a method to generate print notices. This could be a failover from email to print (as overdues do) or a separate cron. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 24562] New: addbiblio.pl overloading CPU
by bugzilla-daemon＠bugs.koha-community.org 31 Dec '23

31 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24562 Bug ID: 24562 Summary: addbiblio.pl overloading CPU Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: jawad_makki(a)hotmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Hello. Sometimes during the day, addbiblio.pl is overloading CPU (100%) and therefore it is making Koha completely not responding for few minutes (can reach 20 minutes). in apache2 log, the response time for "POST /cgi-bin/koha/cataloguing/addbiblio.pl HTTP/1.1" is reaching gateway timeout few times per day. below are some errors retrieved from plack-error.log Use of uninitialized value $mode in string ne at /usr/share/koha/intranet/cgi-bin/cataloguing/addbiblio.pl line 845. Use of uninitialized value $searchid in concatenation (.) or string at /usr/share/koha/intranet/cgi-bin/cataloguing/addbiblio.pl line 876. Koha version 19.11 , running on debian 9 memcached and plack are enabled. this problem was also in 18.11, we have upgraded koha to 19.11 but the problem is still occuring Any help -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 33

[Bug 24207] New: Preferences to select what check in messages need to be displayed
by bugzilla-daemon＠bugs.koha-community.org 31 Dec '23

31 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24207 Bug ID: 24207 Summary: Preferences to select what check in messages need to be displayed 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: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com We would sure like an option to turn on/off each check in message that is displayed. We don't necessarily need to see certain ones, like if the shelving location was changed, or local use is recorded, or that it is not checked out. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 24556] New: Option to toggle certain alerts on check in
by bugzilla-daemon＠bugs.koha-community.org 31 Dec '23

31 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24556 Bug ID: 24556 Summary: Option to toggle certain alerts on check in 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: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com It would be great if libraries had the option to show certain alerts or not. Some libraries do not need to see any/all of the 'Not Check Out' or 'Local Use Recorded', or cart alerts. It pulls their attention unnecessarily to the alert. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 24555] New: POC Elasticsearch - Use boolean queries instead of full text queries
by bugzilla-daemon＠bugs.koha-community.org 31 Dec '23

31 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24555 Bug ID: 24555 Summary: POC Elasticsearch - Use boolean queries instead of full text queries Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: alex.arnaud(a)biblibre.com Here is a proof of concept for replacing current use of full text queries (with query_string) by boolean queries on biblio searches. Advantage: => No search craches with special character ( "!", ")" etc...) => Separate query context and filter context: - Search scores are not altered by facets, - Ability to use range filter (i.e for publication date facet) Also, this POC adds a button "ES query" in the search results header so you can see the query sent to ES. Code is not beautiful, there is no unit test, it's a POC. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 22