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

[Bug 16121] New: Reports need a counter of uses, and date of last use
by bugzilla-daemon＠bugs.koha-community.org 09 Sep '23

09 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16121 Bug ID: 16121 Summary: Reports need a counter of uses, and date of last use Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: gmcharlt(a)gmail.com Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org In an effort to keep reports tidy, it would be helpful if the guided_reports.pl?phase=Use saved, phase=Edit SQL, and phase=Show SQL showed a count of the number of times the report has been run, along with the date it was last run on. This would require two new fields, such as "Use count" and "Last run date". Christopher -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 16109] New: Toolbars wrapping on narrower browsers
by bugzilla-daemon＠bugs.koha-community.org 09 Sep '23

09 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16109 Bug ID: 16109 Summary: Toolbars wrapping on narrower browsers Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleishaamohia(a)hotmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Created attachment 49326 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=49326&action=ed… Buttons on members-toolbar.inc wrapping when I make my browser smaller -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9

[Bug 16093] New: Streamline Holds awaiting pickup cancel process
by bugzilla-daemon＠bugs.koha-community.org 09 Sep '23

09 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16093 Bug ID: 16093 Summary: Streamline Holds awaiting pickup cancel process Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests 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 I would like to suggest some improvements to the Holds over tab in the Holds awaiting pickup tables (waitingreserves.pl): In addition to seeing 13838 pushed to master, I would love to see the following: * Checkboxes next to items, along with a Cancel selected button next to the Cancel All button, with a confirmation. * I haven't confirmed, but if the Cancel all button doesn't already have it, it should also have a confirmation. * Preference to print slips on items that are cancelled individually with the Cancel hold and return to button. * Items that have hold requests should indicate that on the button rather than the "return to" information. * Items that have hold requests end up with TWO statuses on them in this process. They end up with a transfer to the owning library and a hold transfer. In cases where there is a hold request on the item, the transfer status should be skipped and the hold request honored, with the appropriate slip. * If the list is sorted by a particular column, the sort should remain intact when the screen refreshes (bug 13838 solves half the battle by keeping you on the same tab). Christopher -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 24860] New: Add ability to place volume level holds
by bugzilla-daemon＠bugs.koha-community.org 08 Sep '23

08 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24860 Bug ID: 24860 Summary: Add ability to place volume level holds 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com This feature builds upon bug 24857 and allows placing holds that target a specific volume of a record. It is patterned after the feature that allows limiting hold selection by itemtype ( AllowHoldItemTypeSelection ). -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 270

[Bug 16090] New: FK branchcode in issues
by bugzilla-daemon＠bugs.koha-community.org 08 Sep '23

08 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16090 Bug ID: 16090 Summary: FK branchcode in issues Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 2

[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