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

[Bug 30943] New: Make background job classes use helpers
by bugzilla-daemon＠bugs.koha-community.org 14 Mar '23

14 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30943 Bug ID: 30943 Summary: Make background job classes use helpers Change sponsored?: --- Product: Koha Version: unspecified 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: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Bug 30360 introduced helper methods for dealing with starting, marking as finished and also handling progress. Our tasks should use them. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 42

[Bug 24462] New: Adjust K::A::Invoice API mapping to voted RFC
by bugzilla-daemon＠bugs.koha-community.org 14 Mar '23

14 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24462 Bug ID: 24462 Summary: Adjust K::A::Invoice API mapping to voted RFC Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com Now it has been voted, it needs to be adjusted. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 30744] New: Non-public note is visible in OPAC in Title Notes tab
by bugzilla-daemon＠bugs.koha-community.org 14 Mar '23

14 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30744 Bug ID: 30744 Summary: Non-public note is visible in OPAC in Title Notes tab Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org To reproduce: 1. Go to Koha Administration -> Koha bibliographic frameworks 2. View the MARC structure for your BKS framework (or something else) 3. Search for tag 583, edit subfields 4. Go to subfield 'x' - nonpublic note. Confirm the OPAC visibility checkbox is UNCHECKED. 5. Edit or create a record using the BKS framework. Put a note in the 583$x. 6. View this record in the OPAC 7. Go to the Title notes tab. Confirm the non-public note is showing, even though the framework says it should not be visible via the OPAC. -- You are receiving this mail because: You are watching all bug changes.

1 59

[Bug 21009] New: Item URIs longer than 255 bytes are silently truncated
by bugzilla-daemon＠bugs.koha-community.org 14 Mar '23

14 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21009 Bug ID: 21009 Summary: Item URIs longer than 255 bytes are silently truncated Change sponsored?: --- Product: Koha Version: 17.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: paul(a)flo.org QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When creating an item in the staff client Koha does not complain if I paste in (or type) a URI that is longer than 255 bytes. When I save the item, the URI is silently truncated to 255 bytes. Here's a sample URI, 500 bytes long, that you can use to reproduce the bug: http://example.com/harumvelitiustovelitofficiaquisnihilconsecteturisteeumau… -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 32405] New: Add Mastodon account
by bugzilla-daemon＠bugs.koha-community.org 12 Mar '23

12 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32405 Bug ID: 32405 Summary: Add Mastodon account Change sponsored?: --- Product: Project Infrastructure Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Project website Assignee: wizzyrea(a)gmail.com Reporter: david(a)davidnind.com I've created a Mastodon account for Koha - @KohaILS@mastodon.world (https://mastodon.world/@KohaILS) If you are able to add it to the "Community Resources", along with the other social media accounts that would be great! -- You are receiving this mail because: You are watching all bug changes.

1 6

[Bug 19454] New: working title
by bugzilla-daemon＠bugs.koha-community.org 11 Mar '23

11 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19454 Bug ID: 19454 Summary: working title 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: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 39

[Bug 31665] New: 952$d ( Date acquired ) no longer prefills with todays date when focused
by bugzilla-daemon＠bugs.koha-community.org 11 Mar '23

11 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31665 Bug ID: 31665 Summary: 952$d ( Date acquired ) no longer prefills with todays date when focused Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Before the introduction of Flatpickr, when adding a new item if you clicked on the date acquired field, and it was empty, it would be prefilled with today's date. It would be useful if we could get that functionality back. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 27

[Bug 32674] New: When placing a hold in OPAC page explodes into error 500
by bugzilla-daemon＠bugs.koha-community.org 11 Mar '23

11 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32674 Bug ID: 32674 Summary: When placing a hold in OPAC page explodes into error 500 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: jonathan.druart+koha(a)gmail.com When trying to place a hold on a record in the OPAC, we get an error 500 in 22.11.01. The error in the logs is: DBIx::Class::Storage::DBI::_dbh_execute(): DBI Exception: DBD::mysql::st execute failed: Column 'biblionumber' in where clause is ambiguous at /usr/share/koha/lib/Koha/Objects.pm line 394 With Joubu's help we tested following change that fixes the issue: opac/opac-reserve.pl, L.338 - biblionumber => $biblioNumber, + "me.biblionumber" => $biblionumber, There is no test plan as we haven't figured out yet, why this happens for some records and not for others. Items and records look normal, no hidden items on the record and no 773 etc. :) -- You are receiving this mail because: You are watching all bug changes.

1 26

[Bug 32383] New: Indefinite debarments should not be recorded with an expiration date of '9999-12-31'
by bugzilla-daemon＠bugs.koha-community.org 11 Mar '23

11 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32383 Bug ID: 32383 Summary: Indefinite debarments should not be recorded with an expiration date of '9999-12-31' 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: andrewfh(a)dubcolib.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Depends on: 11846 This all might be a regression, looking at Bug 11846 from 2014. To recreate: - have a patron - create a manual restriction for your patron, entering a reason but not a date - confirm that the patron account shows your restriction with an expiration date of "indefinite" - in reports, SELECT * FROM borrower_debarments WHERE borrowernumber= [your patron] - confirm borrower_debarments.expiration is null - in reports, SELECT * FROM borrowers WHERE borrowernumber= [your patron] - confirm borrowers.debarred='9999-12-31' This will cause a lot of issues in 7,977 years. Here in the year 2022, it's generally incorrect and confusing to be using a far-future date to denote "indefinite," and is made more confusing by the fact that borrowers and borrower_debarments don't handle it the same way. This also means one cannot create indefinite debarments via patron import. If one's CSV contains a debarredcomment value without a debarred value, no restriction is created. If one's CSV contains a debarred value of '9999-12-31,' that is treated literally and the restriction is given an expiration date of '9999-12-31.' Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11846 [Bug 11846] Correct database update for debarments with 9999-12-31 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 32576] New: ILL needs the page-section treatment
by bugzilla-daemon＠bugs.koha-community.org 11 Mar '23

11 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32576 Bug ID: 32576 Summary: ILL needs the page-section treatment Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface 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 Blocks: 31757 The ILL module is using panels when it should now use page-section cards instead. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31757 [Bug 31757] Add 'page-section' where it's missing -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 22