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

[Bug 20854] New: Redirect after logout with CAS 3.0 broken
by bugzilla-daemon＠bugs.koha-community.org 24 May '21

24 May '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20854 Bug ID: 20854 Summary: Redirect after logout with CAS 3.0 broken Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org There has been a change in the parameters for the logout request between CAS 2.0 und CAS 3.0: Redirect URL parameter CAS 2.0: url CAS 3.0: service The CAS module used by Koha officially only support CAS 2.0, so when you logout from a CAS 3.0 server now, the redirect to Koha will be broken. See here: https://github.com/apereo/cas/blob/master/docs/cas-server-documentation/pro… Note: The url parameter defined in the former CAS 2.0 specification is not a valid parameter in CAS 3.0 anymore. CAS Servers MUST ignore given url parameters. A CAS client MAY provide the service parameter as described above, as this ensures the parameter is validated against the registered service URLs when operating in non-open mode. See 2.3.2 for details. We are using the following 'hack' to make the redirect work correctly: C4/Auth_with_cas.pm $uri =~ s/\?logout\.x=1//; # We don't want to keep triggering a logout, if we got here, the borrower is already logged out of Koha - print $query->redirect( $cas->logout_url(url => $uri)); + my $logout_url = $cas->logout_url(url => $uri); + $logout_url =~ s/url/service/; + print $query->redirect( $logout_url ); We won't have time to fix this properly, but wanted to document problem and workaround at least. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 30

[Bug 21883] New: Show authorized value description for withdrawn in check-in
by bugzilla-daemon＠bugs.koha-community.org 24 May '21

24 May '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21883 Bug ID: 21883 Summary: Show authorized value description for withdrawn in check-in Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com During check-in (circ/returns.pl) the withdrawn information may be displayed in a message : "Item is withdrawn". Like Bug 21877 we should display the withdrawn authorized value description during check-in. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 39

[Bug 25306] New: Unnecessary update of framework in ModBiblioMarc
by bugzilla-daemon＠bugs.koha-community.org 21 May '21

21 May '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25306 Bug ID: 25306 Summary: Unnecessary update of framework in ModBiblioMarc Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org All calls to this function are either passing the framework obtained from the bib, or precede or are preceded by a bib modification which sets the framework code. We do not need this parameter in this function -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 19

[Bug 23114] New: Inventory: allow to scan barcodes
by bugzilla-daemon＠bugs.koha-community.org 21 May '21

21 May '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23114 Bug ID: 23114 Summary: Inventory: allow to scan barcodes Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: matthias.meusburger(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Currently, in the inventory tool, the user can upload a file containing barcodes. It would be nice for the user to be able to scan barcodes as well, like in other tools (batch item modification, for example). -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 22

[Bug 24986] New: Maximum row size reached soon for borrowers and deletedborrowers
by bugzilla-daemon＠bugs.koha-community.org 18 May '21

18 May '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24986 Bug ID: 24986 Summary: Maximum row size reached soon for borrowers and deletedborrowers Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Running updatedatabase.pl I got the following error messages: DBD::mysql::db do failed: Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs [for Statement "ALTER TABLE borrowers ADD COLUMN autorenew_checkouts TINYINT(1) NOT NULL DEFAULT 1 AFTER anonymized"] at installer/data/mysql/updatedatabase.pl li ne 21259 DBD::mysql::db do failed: Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs [for Statement "ALTER TABLE deletedborrowers ADD COLUMN autorenew_checkouts TINYINT(1) NOT NULL DEFAULT 1 AFTER anonymized"] at installer/data/mysql/updatedatabas e.pl line 21262. After re-injecting an old clean dump and replaying the updatedatabase.pl errors are gone, so it was probably because of other columns coming from patches not yet in master. Maybe we should start moving some columns to other tables. An obvious candidate is all the address fields that can be moved in a patron_addresses table. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 37

[Bug 19873] New: Make it possible to search on value 0
by bugzilla-daemon＠bugs.koha-community.org 17 May '21

17 May '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19873 Bug ID: 19873 Summary: Make it possible to search on value 0 Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: gaetan.boisson(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org The current code considers a value of 0 in a search query as an empty string, that is, it won't search on it. If a library wants to search for records that specifically have the value "0" in a given field, it will not be possible. This patch aims to correct this. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 29

[Bug 23442] New: Add a 'refund' option to the 'Pay' screen
by bugzilla-daemon＠bugs.koha-community.org 13 May '21

13 May '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23442 Bug ID: 23442 Summary: Add a 'refund' option to the 'Pay' screen Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client 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 23354 adds a 'Pay' screen as the beginning of a 'Point of Sale' system. Currently, it only allows for payment of items, but there are occasions where librarians may need to issue a refund. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 92

[Bug 24309] New: Holds on multiple in the same record
by bugzilla-daemon＠bugs.koha-community.org 13 May '21

13 May '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24309 Bug ID: 24309 Summary: Holds on multiple in the same record 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: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Currently there is no way to place simultaneous holds on multiple records in the same record. It would be great if there were a batch feature that would allow you to place holds on multiple items, whether in the same record or not, with the option to specify identical or individual settings (notes, dates, etc) on the items in the batch. Basically, there needs to be something similar to batch item modification, where you can specify a list of barcodes, and the items will load, and you can specify global settings on the holds, or if you fill in something on a specific item, it will not take the global setting. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8

[Bug 15683] New: Inconsistent population of lastreneweddate between AddRenewal and AddIssue
by bugzilla-daemon＠bugs.koha-community.org 12 May '21

12 May '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15683 Bug ID: 15683 Summary: Inconsistent population of lastreneweddate between AddRenewal and AddIssue Change sponsored?: --- Product: Koha Version: 3.20 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When lastreneweddate is populated via C4::Circulation::AddRenewal, it is added as a date, whereas C4::Circulation::AddIssue stores it as DateTime, i.e. hours, minutes and seconds are populated. Because of hourly loans, I think that it only makes sense to store lastreneweddate as a full datetime. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 24154] New: No indication that Default checkout, hold and return policy are set if values are blank
by bugzilla-daemon＠bugs.koha-community.org 12 May '21

12 May '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24154 Bug ID: 24154 Summary: No indication that Default checkout, hold and return policy are set if values are blank Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com To recreate: 1 - Visit Admin->Circulation rules 2 - Go to a specific branch 3 - Clear all the boxes in Default checkout, hold and return policy and save 4 - No visible indication that anything is set 5 - Check the DB, (SELECT * FROM circulation_rules WHERE branchcode='BRANCH') 6 - Note there are rules 7 - Unset the rules, no visible change 8 - Check the D, rules are cleared -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 28