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

[Bug 18532] New: AUTO_RENEWALS should be a patron messaging preferences
by bugzilla-daemon＠bugs.koha-community.org 24 Nov '22

24 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18532 Bug ID: 18532 Summary: AUTO_RENEWALS should be a patron messaging preferences Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Depends on: 15705 The AUTO_RENEWALS notices sent by the automatic_renewals.pl cronjob should be controlled and configurable at user level, like CHECKIN and CHECKOUT That way digest will be supported as well. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15705 [Bug 15705] Notify the user on auto renewing -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 153

[Bug 26539] New: Inconsistent case sensitivity around patron attribute code - potential data loss
by bugzilla-daemon＠bugs.koha-community.org 24 Nov '22

24 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26539 Bug ID: 26539 Summary: Inconsistent case sensitivity around patron attribute code - potential data loss Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: major 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: 1 - have a patron attribute with code "TEST" 2 - using import_borrowers.pl, import a patron with "test:1" in the patron_attributes field of your CSV 3 - load your patron, confirm the value of 1 shows on moremember.pl 4 - click to edit your patron, confirm the value of 1 does not show on memberentry.pl 5 - query the database, SELECT * from borrower_attributes where borrowernumber=[your borrower], see code="test" 6 - update the database, UPDATE borrower_attributes set code="TEST" where id=[your attribute id] 7 - reload memberentry.pl, it now shows a 1 Back at step 4, if we'd saved our patron, that value would have been lost -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 27017] New: Add log trace to EDI Invoice handling
by bugzilla-daemon＠bugs.koha-community.org 22 Nov '22

22 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27017 Bug ID: 27017 Summary: Add log trace to EDI Invoice handling Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: colin.campbell(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org It is useful to log to the trace log the bib numbers affected by Invoice processing. It makes it much easier to establish what processing has occured if any question has been raised -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 26208] New: Overdues restrictions not consistently removed when renewing multiple items at once
by bugzilla-daemon＠bugs.koha-community.org 22 Nov '22

22 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26208 Bug ID: 26208 Summary: Overdues restrictions not consistently removed when renewing multiple items at once 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: 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: - have multiple overdue items on one patron - run overdues.pl with triggers set to generate a restriction - renew all overdues with the Renew All button - restriction is not removed even though patron no longer has overdue items I did not get this error with 5 overdues, but I did get it with 10. Seems like it's due to some messy sequencing when sending a bunch of renewals at once, so it may be inconsistent to recreate. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 37

[Bug 25940] New: Two separate print dialogs when checking in/transferring an item
by bugzilla-daemon＠bugs.koha-community.org 22 Nov '22

22 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25940 Bug ID: 25940 Summary: Two separate print dialogs when checking in/transferring an item 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: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When transferring an item returns.tt is generating multiple print dialogs. I can only recreate this is Chrome but I have heard reports that this is happening in FireFox as well. TO RECREATE: (in Chrome) 1. Have an item belonging to a different branch and check it in. 2. When the modal pops up hit 'Yes, print slip' or 'Print slip' if AutomaticItemReturn is set to 'don't' 3. The first print dialog should appear with a URL like '/cgi-bin/koha/circ/transfer-slip.pl?transferitem=18&&branchcode=CPL&op=slip' 4. Close that print dialog and you will immediately see another one that says 'No slip template found'. 5. Notice the URL of the second pop-up is: /cgi-bin/koha/circ/hold-transfer-slip.pl?reserve_id= 6. There is no reserve id so the template is not found. I cannot recreate this in FireFox and I am unsure why not. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 20

[Bug 23982] New: Count/pagination broken for reports with duplicated column names
by bugzilla-daemon＠bugs.koha-community.org 22 Nov '22

22 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23982 Bug ID: 23982 Summary: Count/pagination broken for reports with duplicated column names 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org bug 23624 simplified how we get the count of rows in a report, however, it breaks under certain circumstances. A report like: SELECT * FROM issues JOIN borrowers USING (borrowernumber) will have two borrowernumber columns - SQL will give us there rsults, but if we try to wrap them in a SELECT COUNT(*) FROM (report) it throws a duplicated column error. I don't know an easy fix except to state that one must name the columns they want to avoid duplication -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 23

[Bug 24372] New: Elasticsearch - cannot search for titles containing a colon next to a search term using the colon
by bugzilla-daemon＠bugs.koha-community.org 22 Nov '22

22 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24372 Bug ID: 24372 Summary: Elasticsearch - cannot search for titles containing a colon next to a search term using the colon Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com Using an example record in the testing DB, try searching for: Pictura murală din nordul Moldovei: modificari estetice si restarare = Mural painting in the north of Moldavia: aesthetic modification and restoration In ES the search fails. If you look at the query we end up with terms like: Moldoveimodificari AND Moldaviaaesthetic This is because of this line in Koha/SearchEngine/Elasticsearch/QueryBuilder.pm 935 # Remove unquoted colons that have whitespace on either side of them 936 $term =~ s/(\:[:\s]+|[:\s]+:)$lookahead//g; Removing colons with a space on either side, we must be careful to put that space back: 936 $term =~ s/(\:[:\s]+|[:\s]+:)$lookahead/ /g; -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 11

[Bug 26626] New: When checking in a hold that is not found the X option is 'ignore' and when hold is found it is 'cancel'
by bugzilla-daemon＠bugs.koha-community.org 20 Nov '22

20 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26626 Bug ID: 26626 Summary: When checking in a hold that is not found the X option is 'ignore' and when hold is found it is 'cancel' 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com This can lead to accidental cancellation if one is simply trying to dismiss the modal and has learned that the X option is often 'ignore' I would suggest replacing 'Ignore/Cancel' with 'Dismiss' and moving the 'Cancel' option to the left of 'Confirm hold' To recreate: 1 - Place a hold for pickup at library A 2 - Checkin the item at Library A 3 - Note the modal has 'Ignore' option 4 - Click it, nothing happens 5 - Check in the item again, same modal 6 - Click 'Confirm' 7 - Check in the item again 8 - Now 'Ignore' is replaced by 'Cancel' 9 - Click 'cancel', but pretend you thought it was 'Ignore' 10 - The book comes up on the holds queue, but no one can find it, because it is on the holds shelf 11 - Then staff do find it, but they hold it for the next patron 12 - The original patron comes in to library, but you won't give them the book, because someone else has the hold now 13 - Drama ensues... -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 33

[Bug 16723] New: Add additional subscription fields to serial claim notices
by bugzilla-daemon＠bugs.koha-community.org 19 Nov '22

19 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16723 Bug ID: 16723 Summary: Add additional subscription fields to serial claim notices Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org It would be nice if it was possible to output the additional subscription fields in the serial related notices - especially the late issue / claim notice. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 23962] New: We should drop support for Debian Jessie during 20.05 cycle.
by bugzilla-daemon＠bugs.koha-community.org 18 Nov '22

18 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23962 Bug ID: 23962 Summary: We should drop support for Debian Jessie during 20.05 cycle. 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org The Debian Jessie LTS support is officially coming to an end on June 30, 2020. We should continue to support the stable releases until that time (and perhaps for a short period afterwards) but publicise an official drop of support with our 20.05 release as we can't/shouldn't really officially support 20.05 on Jessie for more than a month after it's release (i.e. after Debian has dropped such support itself) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3