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

[Bug 27542] New: It should be possible to cancel a request sent to a partner
by bugzilla-daemon＠bugs.koha-community.org 08 Sep '23

08 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27542 Bug ID: 27542 Summary: It should be possible to cancel a request sent to a partner Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew.isherwood(a)ptfs-europe.com After an ILL request has "Place request with partner libraries" status, is it no longer possible to cancel it via the "Revert request" option as this button is not displayed. This should be possible. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 29

[Bug 27678] New: Add option to exclude facets in search results
by bugzilla-daemon＠bugs.koha-community.org 07 Sep '23

07 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27678 Bug ID: 27678 Summary: Add option to exclude facets in search results Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: severine.queune(a)bulac.fr QA Contact: testopia(a)bugs.koha-community.org All we can do for now with facet is select them, but it could be useful if we can exclude them in the search results, using for example a checkbox on the right of the facet ? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 26030] New: Allow to explicitly search for a hidden ILL status
by bugzilla-daemon＠bugs.koha-community.org 07 Sep '23

07 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26030 Bug ID: 26030 Summary: Allow to explicitly search for a hidden ILL status Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de Bug 23391 allows to hide ILL status from search which is part of a performance fix by allowing to remove finished ILL from the big ILL request table. It would be nice if we could allow to search by the hidden status when someone chooses to do so. Not including them in the default search, but allowing for them to be a search criteria. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 26035] New: AutoMemberNum fails on very large cardnumbers
by bugzilla-daemon＠bugs.koha-community.org 06 Sep '23

06 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26035 Bug ID: 26035 Summary: AutoMemberNum fails on very large cardnumbers Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons 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, kyle.m.hall(a)gmail.com To recreate: - create a borrower with cardnumber 603628999632182575912 - turn on automembernum - create a new patron, save without a cardnumber - see that your new patron has cardnumber 0 As part of the fixup_cardnumber sub in Patron.pm, we CAST(cardnumber AS SIGNED), which tries to make the cardnumber into a 64 bit integer. Way back in bug 13178, we increased the max length of a cardnumber to 32 characters, which is longer than a 64 bit integer can handle. So the CAST spits out a -1, to which Koha adds 1, arriving at cardnumber 0. Why do we cast it as signed in the first place? I don't understand enough about integers to see what purpose this is serving. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14

[Bug 29578] New: Search term highlighting breaks with titles containing characters with Greek diacritics
by bugzilla-daemon＠bugs.koha-community.org 06 Sep '23

06 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29578 Bug ID: 29578 Summary: Search term highlighting breaks with titles containing characters with Greek diacritics Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: a.roussos(a)dataly.gr QA Contact: testopia(a)bugs.koha-community.org The commits from Bug 5844 and Bug 20501 fixed the problem of DOM content disappearing from the results of OPAC/Staff Client searches under certain conditions (e.g. when the search terms were "magaz mag" or "the the"). However, there is still a case where the jQuery term highlighter can break, and in the process actually make the "Highlight"/"Unhighlight" button disappear altogether! To reproduce, catalogue two books using the titles below, one of which includes a word ("τοῖς") [1] containing Greek diacritics: Title #1: Συλλογής των εν επιτομή τοῖς πάλαι γεωγραφηθέντων Title #2: Επιτομή της ιστορίας των Βαλκανικών Πολέμων (1912-1913) Then, perform a catalog search for "επιτομή των" (without the quotes). You should get what is depicted in the attached screenshots. Notice how 1) the "Highlight"/"Unhighlight" button has disappeared, and 2) not all search terms are highlighted (e.g. "των" in the 2nd result) If using Firefox, in the Browser Console the following error will be logged: Uncaught DOMException: Index or size is negative or greater than the allowed amount The offending file is koha-tmpl/opac-tmpl/bootstrap/lib/jquery/plugins/jquery.highlight-3.js, line 26: 26 var endbit = middlebit.splitText(pat.length); Upgrading the plugin from its current version (v3) to the latest version available [1] from the developer (v5) fixes the problem. Please note that the changes to this script from commit 2e4b574074 should also be incorporated. [1] https://en.wiktionary.org/wiki/%CF%84%CE%BF%E1%BF%96%CF%82 [2] https://johannburkard.de/blog/programming/javascript/highlight-javascript-t… -- You are receiving this mail because: You are watching all bug changes.

1 47

[Bug 23520] New: Error: invalid_request using Google OpenID Authentication
by bugzilla-daemon＠bugs.koha-community.org 06 Sep '23

06 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23520 Bug ID: 23520 Summary: Error: invalid_request using Google OpenID Authentication Change sponsored?: --- Product: Koha Version: 17.11 Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: gcastellano(a)nosturi.es QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org Hi there, We are trying unsuccessfully to connect an instance of Koha 17.11.18.000 to Google OpenID following the instructions provided here: https://koha-community.org/manual/17.11/html/02_administration.html?highlig…. This is the error that we get: 400. That’s an error. Error: invalid_request Invalid parameter value for redirect_uri: Missing scheme: /cgi-bin/koha/svc/auth/googleopenidconnect Learn more Request Details response_type=code redirect_uri=/cgi-bin/koha/svc/auth/googleopenidconnect client_id=151271246332-2rutdao24k2as059d4ht7gmo0utln43l.apps.googleusercont… scope=openid email profile state=auth_660a4a0ed00714e959894abe360a3532 That’s all we know. We have checked that we have a client ID and a client secret; and that the authorized JavaScript origins, as well as the authorized redirect URLs, match the URL of the OPACBaseURL and http://YOUROPAC/cgi-bin/koha/svc/auth/googleopenidconnect <http://YOUROPAC/cgi-bin/koha/svc/auth/googleopenidconnect>. We have also checked that the values of GoogleOAuth2ClientID and GoogleOAuth2ClientSecret in Koha match the values of the Google client ID and the client secret. We are not sure whether we are missing something or there is something wrong in the docs, Koha 17.11 or the connector. Many thanks in advance. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 27448] New: Update ElasticsearchCrossFields description to explain consequences of setting in Koha
by bugzilla-daemon＠bugs.koha-community.org 06 Sep '23

06 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27448 Bug ID: 27448 Summary: Update ElasticsearchCrossFields description to explain consequences of setting in Koha Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com The description of the ElasticsearchCrossFields is technical correct, but for someone configuring Koha, it's not clear what the settings mean for using Koha. What's the consequence of choosing one setting or the other? It's only clear that you will need to use a specific Elasticsearch version. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8

[Bug 25891] New: build_holds_queue can be daemonised
by bugzilla-daemon＠bugs.koha-community.org 04 Sep '23

04 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25891 Bug ID: 25891 Summary: build_holds_queue can be daemonised Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz We have customers who have come from systems where the holds queue is either dynamically built at query time or where it's being much more regularly updated. In their workflows, having to wait for an hour between runs is an annoyance. With the recent introduction of easy locking mechanisms via the Koha::Script class we should be able to utilise this functionality to allow the build_holds_queue job to be demonized such that it runs on a loop. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 23995] New: Check constraints are supported differently by MySQL and MariaDB so we should remove them for now.
by bugzilla-daemon＠bugs.koha-community.org 01 Sep '23

01 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23995 Bug ID: 23995 Summary: Check constraints are supported differently by MySQL and MariaDB so we should remove them for now. Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Database Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org We had two check constraints in kohastructure.. MariaDB and MySQL have now both implimented support for such constraints, but decided to use different, incompatible, syntaxes. As such, we should remove the current check constraints until a time when we have a better understanding on how to work around these differences. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 29129] New: The printclearscreen icon on circulation.tt should be configuarable to print either ISSUESLIP or ISSUEQSLIP
by bugzilla-daemon＠bugs.koha-community.org 01 Sep '23

01 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29129 Bug ID: 29129 Summary: The printclearscreen icon on circulation.tt should be configuarable to print either ISSUESLIP or ISSUEQSLIP 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: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com The printclearscreen icon which appears when the system preference 'DisplayClearScreenButton' should allow users to choose between printing the ISSUESLIP and ISSUEQSLIP, if that system pref is turned on. I think the 'DisplayClearScreenButton' could have 3 options: -Don't show -Show and print ISSUESLIP -Show and print ISSUEQSLIP -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 30