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

[Bug 27424] New: One should be able to assign an SMTP server as the default
by bugzilla-daemon＠bugs.koha-community.org 08 Sep '23

08 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27424 Bug ID: 27424 Summary: One should be able to assign an SMTP server as the default 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Bug 22343 adds the ability to defined SMTP servers via the UI; But to then utilise them you have to go to each individual library via the libraries admin area and select the SMTP server. We should have a way to override the fallback/default SMTP server right from the SMTP servers administration page.. setting one of our defined SMTP Servers as the system default rather than using the hard coded fallback options. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 66

[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 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 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 18066] New: Hea - Version 2
by bugzilla-daemon＠bugs.koha-community.org 01 Sep '23

01 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18066 Bug ID: 18066 Summary: Hea - Version 2 Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: System Administration Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com I plan to submit a big improvement for Hea (https://wiki.koha-community.org/wiki/KohaUsageStat_RFC) The different goals are: 1/ Add more information on how Hea is collecting the data and what we do with them 2/ Collect geolocation to display the Koha installations on a map 3/ Collect data per library instead of per Koha installation -- You are receiving this mail because: You are watching all bug changes.

1 68

[Bug 24359] New: Remove items from Holds Queue when checked in
by bugzilla-daemon＠bugs.koha-community.org 31 Aug '23

31 Aug '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24359 Bug ID: 24359 Summary: Remove items from Holds Queue when checked in Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: joy(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Currently, if an item is checked in and the hold is triggered/captured, the item will not come off the holds queue until the the cronjob runs again. This causes some confusion for multibranch systems when other branches attempt to fill holds that have already been filled. Proposal: Remove bib/items from the Holds Queue after checkin and before the next holds queue cron runs to update the holds queue. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 41