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

[Bug 19444] New: Automatic renewal script should not auto-renew if a patron' s record has expired
by bugzilla-daemon＠bugs.koha-community.org 23 Nov '21

23 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19444 Bug ID: 19444 Summary: Automatic renewal script should not auto-renew if a patron's record has expired 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: janet.mcgowan(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Currently with the automatic_renewals.pl script, materials are still auto-renewed even if the patron's account has expired. The automatic renewals script has error conditions which prevent automatic renewals in these circumstances: $error eq 'too_many' or $error eq 'on_reserve' or $error eq 'restriction' or $error eq 'overdue' or $error eq 'auto_too_late' or $error eq 'auto_too_much_oweing' or $error eq 'auto_too_soon The error conditions should take into account the expiry date of borrower and not auto renew if the borrower's account has expired. For example adding a new error code such as 'borrower_expired' - or whatever convention achieves this. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 38

[Bug 17979] New: Fatal error when searching from addbooks.pl due to ISBN flaw
by bugzilla-daemon＠bugs.koha-community.org 23 Nov '21

23 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17979 Bug ID: 17979 Summary: Fatal error when searching from addbooks.pl due to ISBN flaw Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org If you're doing a "Cataloging Search" from /cgi-bin/koha/cataloguing/addbooks.pl, and you type in "1st to die", you'll see the following: DBD::mysql::st execute failed: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near '' at line 5 at /<koha>/lib/C4/Breeding.pm line 107 The reason is that the string is 10 characters long and contains a digit, so Koha thinks it's an ISBN. But when it tries to normalize it, it fails, and instead Koha generates no data for the WHERE clause and then the SQL statement fails because it contains a WHERE without the actual clause. The code: if ($query) { # fill isbn or title, depending on what has been entered #u must do check on isbn because u can find number in beginning of title #check is on isbn legnth 13 for new isbn and 10 for old isbn my ( $title, $isbn ); if ($query=~/\d/) { my $clean_query = $query; $clean_query =~ s/-//g; # remove hyphens my $querylength = length $clean_query; if ( $querylength == 13 || $querylength == 10 ) { $isbn = $query; } } if (!$isbn) { $title = $query; } ( $countbr, @resultsbr ) = BreedingSearch( $title, $isbn ); } -- You are receiving this mail because: You are watching all bug changes.

1 27

[Bug 25429] New: Cleanup Database - remove resolved claims returned from db after X days
by bugzilla-daemon＠bugs.koha-community.org 23 Nov '21

23 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25429 Bug ID: 25429 Summary: Cleanup Database - remove resolved claims returned from db after X days 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: joy(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Add option to cleanup_database script to removed 'resolved' return claims from the database after a specified number of days. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 78

[Bug 26374] New: Update for 19974 is not idempotent
by bugzilla-daemon＠bugs.koha-community.org 23 Nov '21

23 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26374 Bug ID: 26374 Summary: Update for 19974 is not idempotent 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 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 24

[Bug 24406] New: Remove patron category category type codes from patron search results
by bugzilla-daemon＠bugs.koha-community.org 22 Nov '21

22 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24406 Bug ID: 24406 Summary: Remove patron category category type codes from patron search results Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons 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, kyle.m.hall(a)gmail.com In the patron search, the category type of a patron will show after the patron category description. Example: Student (A) This is confusing as those codes (A = Adult) show nowhere else in the staff interface and can't be easily translated by people using the English templates, but have even less meaning for people using translated templates. I suggest to remove them as I always end up explaining this in training and it's not really useful information. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 17423] New: patronimage.pl permission is too restrictive
by bugzilla-daemon＠bugs.koha-community.org 22 Nov '21

22 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17423 Bug ID: 17423 Summary: patronimage.pl permission is too restrictive Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Patrons 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 Bug 14566 added the permission "borrowers" on patronimage.pl. This perm is too restrictive because circulation pages also uses this page. I propose to simply use "catalogue" perm. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 24305] New: Batch Item modification via item number in reports does not work with CONCAT in report
by bugzilla-daemon＠bugs.koha-community.org 22 Nov '21

22 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24305 Bug ID: 24305 Summary: Batch Item modification via item number in reports does not work with CONCAT in report Change sponsored?: --- Product: Koha Version: 19.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: bwsdonna(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl If you have a report with a CONCAT statement in it, and use that report to pass the item numbers to the batch item modification, the batch modification does not work. Title list does not show, just the edit item screen, and if you proceed, nothing is modified. To create, use a report such as: SELECT items.biblionumber,items.itemcallnumber,items.itype,biblio.author,biblio.title, biblio.copyrightdate, items.barcode, items.location,CONCAT('<a href=\"/cgi-bin/koha/cataloguing/additem.pl?op=edititem&biblionumber=', biblionumber, '&itemnumber=', itemnumber, '#edititem', '\">', itemnumber, '</a>' ) AS itemnumber FROM biblio JOIN items USING (biblionumber) WHERE (items.location IS NULL OR items.location = '') ORDER by items.itemcallnumber ASC and see that the batch modification is blank. Remove the concat statement, and the batch item modification works as expected. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 31

[Bug 24665] New: Add ability to Run Cash Register report with New Cash register feature
by bugzilla-daemon＠bugs.koha-community.org 22 Nov '21

22 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24665 Bug ID: 24665 Summary: Add ability to Run Cash Register report with New Cash register feature Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: martin.renvoize(a)ptfs-europe.com Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org With the introduction of Cash Registers in 19.11, it would be ideal if a library could run the "Cash register" report (found under Statistic Wizard in Reports) and specifically choose to refine the report to a specific Cash Register. -- You are receiving this mail because: You are watching all bug changes.

1 33

[Bug 26272] New: Allow cashup summaries to be displayed from the library summary page
by bugzilla-daemon＠bugs.koha-community.org 22 Nov '21

22 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26272 Bug ID: 26272 Summary: Allow cashup summaries to be displayed from the library summary page Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 26172 Blocks: 13985 With bug 26172 we add a nice display for the most recent cashup to have taken place on a cash register. We should add the ability to display this same data, per register, from the cash management library details page. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13985 [Bug 13985] Cash Management - Koha as 'Point of Sale' https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26172 [Bug 26172] Add a cashup summary view -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 27

[Bug 26273] New: Expose cashup summary historyfor a cash register
by bugzilla-daemon＠bugs.koha-community.org 22 Nov '21

22 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26273 Bug ID: 26273 Summary: Expose cashup summary historyfor a cash register Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 26272 Blocks: 13985 With bug 26172 we allow for a nicely summarised display of cash register activity for the most recent cashup action. We should somehow expose the ability to see past cashups in the same way. I'm open to suggestions on how best to expose this... one thought that came to mind was to add 'next/previous' buttons to the summary modal so you could 'scroll' through previous cashups.. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13985 [Bug 13985] Cash Management - Koha as 'Point of Sale' https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26272 [Bug 26272] Allow cashup summaries to be displayed from the library summary page -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 80