May 2023 - Koha-bugs - lists.koha-community.org

[Bug 28051] New: On upgrade to 19.11, per-item Writeoff got confused with Lost
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '23

01 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28051 Bug ID: 28051 Summary: On upgrade to 19.11, per-item Writeoff got confused with Lost Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: pongtawat(a)punsarn.asia QA Contact: testopia(a)bugs.koha-community.org During upgrade to 19.11, database upgrade script introduced by Bug #22563 (convert "lost" handling) also handle case of normal per-item writeoff like those writeoff generated from lost. So, all patron with normal per-item writeoff will now see additional account line of 'LOST' type. This is due to the following code in updatedatabase.pl: # Find and correct pathalogical cases of L having been converted to W $sth = $dbh->prepare( "SELECT accountlines_id, issue_id, borrowernumber, itemnumber, amount, manager_id FROM accountlines WHERE accounttype = 'W' AND itemnumber IS NOT NULL" ); ... Step to reproduce: 1. Start with Koha 18.05. 2. Create overdue fine on item X for patron A, amount=100. 3. Per-item write-off amount=50 on item X for patron A. This will create 'W' line in accountlines with amount=50 and item=X 4. Upgrade to Koha 19.11 or later (in our case 20.05) 5. Patron A now has an additional 'LOST' with amount=50 and item=X in their accountlines. This additional 'LOST' line is incorrect in this case. Also, I notice that this per-item writeoff is in debit side (red). I don't know if this is correct or not, but shouldn't writeoff be on credit side? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 28049] New: Elements on most staff interface pages move tiny bit after page is fully reloaded
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '23

01 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28049 Bug ID: 28049 Summary: Elements on most staff interface pages move tiny bit after page is fully reloaded Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: joonas.kylmala(a)helsinki.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com When you load most Koha staff interface pages, e.g. front page, you notice that the HTML elements on the page move slightly after the page is fully loaded. This seems to happen because of the Search bar changing its size tiny bit probably due to some JS stuff. You can also easily reproduce the problem by clicking on the Koha search text box and then clicking outside of it, you should notice the slight movement of the HTML elements. This is annoying and causes misclicks! -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 28029] New: Add ability to use OFFSET in SQL reports
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '23

01 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28029 Bug ID: 28029 Summary: Add ability to use OFFSET in SQL reports Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: joe(a)flo.org QA Contact: testopia(a)bugs.koha-community.org As far as I can tell, you can't use offset [# to offset] or the abbreviated limit [# to offset], [# to limit] shorthand to offset your results in Koha's SQL reports. These features are available in MySQL and Mariadb, so it would be nice if you could use one of them on the front end. Here are two simple examples that don't work: select borrowernumber from borrowers limit 10, 10 select borrowernumber from borrowers limit 10 offset 10 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 28025] New: allow option for when to send autorenew denied/onhold notices
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '23

01 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28025 Bug ID: 28025 Summary: allow option for when to send autorenew denied/onhold notices Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: bwsdonna(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Bug 19014 changed when autorenew notices for items with a hold on them was sent. Some libraries have asked for the option to decide when those notices will be sent. For example: Item is checked out on March 1 and has holds on it. Autorenew set for 0, so patrons will get the no-renewal notice the day the item is due. The library would like to send the no autorenew notice perhaps 5 days prior to the due date, independent of actually trying to renew the item. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 28024] New: Remove X-Abuse-Report header adding in opac-sendbasket.pl
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '23

01 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28024 Bug ID: 28024 Summary: Remove X-Abuse-Report header adding in opac-sendbasket.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org I'm reporting this mainly to hear from other devs. I found opac-sendbasket.pl is the only place Koha sets that header, and a search tells me it is not standard and is used with several (other) names. In my opinion, such custom header should be configurable, or totally handled in the MTA. And if it was something that should be configurable or even mandatory, shouldn't it be set for all emails? At Koha::Email? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 28008] New: Patron Clubs Bulk Enrollment
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '23

01 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28008 Bug ID: 28008 Summary: Patron Clubs Bulk Enrollment Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: bwsdonna(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org With Patron Clubs, there is not a way to add a group/list/multiple patrons to a club. Patrons have to be added individually. It would be helpful to be able to a list of patrons to a club, and be able to add patrons to a club from a patron search. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 31241] New: PDF export of ANY label is NOT functioning.
by bugzilla-daemon＠bugs.koha-community.org 30 Jun '23

30 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31241 Bug ID: 31241 Summary: PDF export of ANY label is NOT functioning. Change sponsored?: --- Product: Koha Version: 22.05 Hardware: All OS: All Status: NEW Severity: blocker Priority: P5 - low Component: Label/patron card printing Assignee: cnighswonger(a)foundations.edu Reporter: stdominic.novices(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org I've been experimenting and no label type of any kind works when exported as a pdf. Either it is completely jumbled or massive amounts of the data are missing. I've tried batch and selected exporting, redoing the layouts and templates. This is for Patron, barcode, and spine label. I have a similar bug concerning the spine label, but this seems to be a more widespread problem than I first thought. If I try to export a singly selected or any other number that is not the full batch I get an Error 500 message, and if it's the full bath the label is garbled. Thanks for your time looking into this! -- You are receiving this mail because: You are watching all bug changes.

1 10

[Bug 16665] New: Add a staffadmin bar to the opac interface in order to edit the previewing record (MARC)
by bugzilla-daemon＠bugs.koha-community.org 30 Jun '23

30 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16665 Bug ID: 16665 Summary: Add a staffadmin bar to the opac interface in order to edit the previewing record (MARC) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: dimantonak(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Currently when a librarian previewing a record in the opac interface and wants to edit that record, has to go to the staff interface, search again for that record and edit it. It would be useful to add a staffadmin bar (IF a librarian is logged in) linking to the staff interface (cgi-bin/koha/catalogue/detail.pl?biblionumber=#) in order to edit the MARC record directly. -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 33800] New: Error 500 in issues_stats.pl
by bugzilla-daemon＠bugs.koha-community.org 30 Jun '23

30 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33800 Bug ID: 33800 Summary: Error 500 in issues_stats.pl Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: eugenegf(a)yahoo.com QA Contact: testopia(a)bugs.koha-community.org We're in Koha 22.11.04 and in "/cgi-bin/koha/reports/borrowers_stats.pl" and just the default "itemtype" and "issuing library" buttons ticked, cell value = count total items and output = "to screen into browser". After submitting, we're getting "Error 500". In the log, we were getting this: [2023/05/23 10:13:49] [WARN] Argument "2023-05-01" isn't numeric in numeric lt (<) at /usr/share/koha/intranet/cgi-bin/reports/issues_stats.pl line 214. [2023/05/23 10:13:49] [WARN] Argument "2023-05-31" isn't numeric in numeric lt (<) at /usr/share/koha/intranet/cgi-bin/reports/issues_stats.pl line 214. This worked in previous Koha ILS version. It seems there is a bug. Thanks! -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[Bug 26351] New: Add plugin hooks to transform item barcodes
by bugzilla-daemon＠bugs.koha-community.org 30 Jun '23

30 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26351 Bug ID: 26351 Summary: Add plugin hooks to transform item barcodes Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Plugin architecture Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Moved from bug 25712 Some of our partners have unusual barcode requirements that have required us to transform scanned barcodes using javascript. This is not the most reliable method. It would make more sense to have Koha transform the barcodes on the backend using a plugin. We should add hooks to transform and generate new item and patron barcodes. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 143