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

[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 29971] New: Remember selections across patron search pages
by bugzilla-daemon＠bugs.koha-community.org 07 Sep '23

07 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29971 Bug ID: 29971 Summary: Remember selections across patron search pages Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Patrons Assignee: oleonard(a)myacpl.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 Blocks: 28366 I'd like to modify the patron search results page so that when the user checks a checkbox for a patron, the page remembers that selection even after they click to a different page of search results. This will allow the user to select patrons across pages, have the checkbox state persist, and be able to pass all selected patrons to a list or a merge operation. My goal is to have this in place for Bug 28366, "Add batch patron modification to patron search results." Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28366 [Bug 28366] Add batch patron modification to patron search results -- You are receiving this mail because: You are watching all bug changes.

1 35

[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 31584] New: Default indicators not taken into account when creating records using UseACQFrameworkForBiblioRecords
by bugzilla-daemon＠bugs.koha-community.org 06 Sep '23

06 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31584 Bug ID: 31584 Summary: Default indicators not taken into account when creating records using UseACQFrameworkForBiblioRecords Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org When using UseACQFrameworkForBiblioRecords default indicators are not added to the record as configured in the ACQ framework. For a test: * Create 264 abc in your ACQ framework, set second indicator to default 1 * Create an order using the form * Verify the indicator hasn't been set For some fields where the label shown depends on the indicator, this creates a display issue. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 29664] New: Do not show voided payments in cash_register_stats.pl
by bugzilla-daemon＠bugs.koha-community.org 05 Sep '23

05 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29664 Bug ID: 29664 Summary: Do not show voided payments in cash_register_stats.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org To recreate: - take a payment of $1 - void that payment - go to reports, Cash Register (cash_register_stats.pl) and run a report for all payments taken today, see your voided payment We should not included voided credits, it throws off the totals. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 36

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

05 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 30584] New: Cannot add field mappings to Elasticsearch configuration
by bugzilla-daemon＠bugs.koha-community.org 01 Sep '23

01 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30584 Bug ID: 30584 Summary: Cannot add field mappings to Elasticsearch configuration 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 29893 redraws the table before submission - this appears to remove any rows we have added To test: 1 - Browse to Administration -> Catalog -> Search engine configuration (Elasticsearch) 2 - Click on 'Bibliographic records' tab 3 - Scroll to bottom and enter a new mapping and click '+Add' button at far right 4 - Click 'Save' button at bottom 5 - You may notice your new row disappears, then the page reloads 6 - Check for your new mapping - it has not been added -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16