February 2021 - Koha-bugs - lists.koha-community.org

[Bug 20417] New: Remove OpacCloud system preference and feature
by bugzilla-daemon＠bugs.koha-community.org 02 May '22

02 May '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20417 Bug ID: 20417 Summary: Remove OpacCloud system preference and feature Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: gaetan.boisson(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org This is a poorly implemented old fashioned "word cloud". I think it could be entirely removed. -- You are receiving this mail because: You are watching all bug changes.

1 10

[Bug 24074] New: Access directory UX improvements
by bugzilla-daemon＠bugs.koha-community.org 02 May '22

02 May '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24074 Bug ID: 24074 Summary: Access directory UX improvements Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: wizzyrea(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com I noticed a few things about this feature when I was setting it up (which by the way, I LIKE A LOT!!) - We cannot do subdirectories here. We should allow that? - Multiple access directories don't show the path, that seems like useful information we should have - either we should pick the directory we want before we see the list, or we should show the path to the file. An example of a use case would be that a library wants to put their print notices there, but they also put other things in that access directory. They may only want to see the directory that has the notices in it. Currently we can't do that. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 25674] New: Add RabbitMQ options to koha-create
by bugzilla-daemon＠bugs.koha-community.org 29 Apr '22

29 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25674 Bug ID: 25674 Summary: Add RabbitMQ options to koha-create Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Installation and upgrade (command-line installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Now that we plan to use RabbitMQ as message broken for a task queue manager, we need to be able to set the RabbitMQ options on instance creation. It should fallback to localhost, etc. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 52

[Bug 27756] New: background_jobs_worker.pl is memory inefficient
by bugzilla-daemon＠bugs.koha-community.org 29 Apr '22

29 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27756 Bug ID: 27756 Summary: background_jobs_worker.pl is memory inefficient 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: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org Once Perl allocates memory, it doesn't return that memory to the Operating System for the life of that Perl process. If memory is freed within a Perl program (nullifying a variable, for instance), that memory will be re-used within the Perl program, but it will not return the memory. This can cause unexpected excessive memory consumption for long-running Perl programs. misc/background_jobs_worker.pl runs all its code within the same process, so it will never return allocated memory. This means that 1 large background import could cause background_jobs_worker.pl to permanently use a large amount of memory (until it is restarted). The solution is to do the background work within a forked process. I was reminded of this when I read "The worker process will fork a new process for every job that is being processed. This allows for resources such as memory to be returned to the operating system once a job is finished. Perl fork is very fast, so don't worry about the overhead" at https://docs.mojolicious.org/Minion. It's the same premise as bug 27267. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19

[Bug 27077] New: Searching for patrons with guarantor_id criteria results in 500 error
by bugzilla-daemon＠bugs.koha-community.org 28 Apr '22

28 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27077 Bug ID: 27077 Summary: Searching for patrons with guarantor_id criteria results in 500 error Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: arthur.suzuki(a)biblibre.com Tried to fetch all patrons who's guarantor is "someone", got 500 error. Due to changes in the borrower table to permit multiple guarantor. Curl command : <pre> curl http://localhost:8080/api/v1/patrons?guarantor_id=42 \ -H 'Authorization: Basic a29oYTprb2hh' </pre> Plack error log : <pre> [2020/11/23 10:20:33] [WARN] Use of uninitialized value $column_type in string eq at /kohadevbox/koha/Koha/Object.pm line 447. [2020/11/23 10:20:33] [WARN] DBD::mysql::st execute failed: Unknown column 'guarantorid' in 'where clause' [for Statement "SELECT `me`.`borrowernumber`, `me`.`cardnumber`, `me`.`surname`, `me`.`firstname`, `me`.`title`, `me`.`othernames`, `me`.`initials`, `me`.`streetnumber`, `me`.`streettype`, `me`.`address`, `me`.`address2`, `me`.`city`, `me`.`state`, `me`.`zipcode`, `me`.`country`, `me`.`email`, `me`.`phone`, `me`.`mobile`, `me`.`fax`, `me`.`emailpro`, `me`.`phonepro`, `me`.`B_streetnumber`, `me`.`B_streettype`, `me`.`B_address`, `me`.`B_address2`, `me`.`B_city`, `me`.`B_state`, `me`.`B_zipcode`, `me`.`B_country`, `me`.`B_email`, `me`.`B_phone`, `me`.`dateofbirth`, `me`.`branchcode`, `me`.`categorycode`, `me`.`dateenrolled`, `me`.`dateexpiry`, `me`.`date_renewed`, `me`.`gonenoaddress`, `me`.`lost`, `me`.`debarred`, `me`.`debarredcomment`, `me`.`contactname`, `me`.`contactfirstname`, `me`.`contacttitle`, `me`.`borrowernotes`, `me`.`relationship`, `me`.`sex`, `me`.`password`, `me`.`flags`, `me`.`userid`, `me`.`opacnote`, `me`.`contactnote`, `me`.`sort1`, `me`.`sort2`, `me`.`altcontactfirstname`, `me`.`altcontactsurname`, `me`.`altcontactaddress1`, `me`.`altcontactaddress2`, `me`.`altcontactaddress3`, `me`.`altcontactstate`, `me`.`altcontactzipcode`, `me`.`altcontactcountry`, `me`.`altcontactphone`, `me`.`smsalertnumber`, `me`.`sms_provider_id`, `me`.`privacy`, `me`.`privacy_guarantor_fines`, `me`.`privacy_guarantor_checkouts`, `me`.`checkprevcheckout`, `me`.`updated_on`, `me`.`lastseen`, `me`.`lang`, `me`.`login_attempts`, `me`.`overdrive_auth_token`, `me`.`anonymized`, `me`.`autorenew_checkouts` FROM `borrowers` `me` WHERE ( `guarantorid` LIKE ? )" with ParamValues: 0="%42%"] at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1836. </pre> -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 22204] New: Leading spaces in barcode should not allowed in cataloguing
by bugzilla-daemon＠bugs.koha-community.org 28 Apr '22

28 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22204 Bug ID: 22204 Summary: Leading spaces in barcode should not allowed in cataloguing Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Target Milestone: --- When creating a new item, it is not allowed to add trailing spaces, it shows 'Barcode must be unique'. But it is allowed to use leading spaces :( In this case since circulation does a trim on barcode this item can not be checked-out. It also allows duplicates even with UNIQUE KEY constraint. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 29

[Bug 23070] New: Use Koha::Hold in C4::Reserves::RevertWaitingStatus
by bugzilla-daemon＠bugs.koha-community.org 27 Apr '22

27 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23070 Bug ID: 23070 Summary: Use Koha::Hold in C4::Reserves::RevertWaitingStatus Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 9834 Target Milestone: --- We are using raw SQL statements, we should use Koha::Hold instead. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9834 [Bug 9834] Reverting a waiting hold should lead to the former hold type (item or biblio level) -- You are receiving this mail because: You are watching all bug changes.

1 51

[Bug 25703] New: AllowItemsOnHoldCheckoutSCO behavior.
by bugzilla-daemon＠bugs.koha-community.org 27 Apr '22

27 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25703 Bug ID: 25703 Summary: AllowItemsOnHoldCheckoutSCO behavior. Change sponsored?: --- Product: Koha Version: 19.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Self checkout Assignee: koha-bugs(a)lists.koha-community.org Reporter: eveal(a)mckinneytexas.org QA Contact: testopia(a)bugs.koha-community.org The AllowItemsOnHoldCheckoutSCO syspref allows all items on hold to be checkout within the selfcheck module. It seems to me that the preference would be more useful if it only allowed items with "Pending" holds not "confirmed and waiting" holds. Ed -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 24561] New: Add embedded column filter feature to datatables api wrapper
by bugzilla-daemon＠bugs.koha-community.org 27 Apr '22

27 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24561 Bug ID: 24561 Summary: Add embedded column filter feature to datatables api wrapper Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: agustinmoyano(a)theke.io Reporter: agustinmoyano(a)theke.io QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com Depends on: 20212, 24502 Blocks: 20936 Bug 24502 introduced filtering by embedded columns. It would be great if datatables wrapper for the API in bug 20212 could use this feature. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20212 [Bug 20212] Slowness in Receiving in Acquisitions https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20936 [Bug 20936] Holds History for patrons in OPAC https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24502 [Bug 24502] Add a query language and param (q=) to the API -- You are receiving this mail because: You are watching all bug changes.

1 43

[Bug 22279] New: Unify patron name display
by bugzilla-daemon＠bugs.koha-community.org 27 Apr '22

27 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22279 Bug ID: 22279 Summary: Unify patron name display Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: pasi.kallinen(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- The way patron's name is displayed should be unified into a single place. There's template code in patron-title.inc for it, but it's not used in enough places. Using that would make the patron name display consistent, and if change is needed (eg. for GDPR), it would be easy to change. For example: koha-tmpl/intranet-tmpl/prog/en/includes/cat-toolbar.inc: <li><a href="/cgi-bin/koha/reserve/request.pl?biblionumber=[% biblionumber | uri %]&findborrower=[% holdfor_cardnumber | uri %]">Place hold for [% holdfor_firstname | html %] [% holdfor_surname | html %] ([% holdfor_cardnumber | html %])</a></li> koha-tmpl/intranet-tmpl/prog/en/includes/js_includes.inc: .append( "<a>" + item.surname + ", " + item.firstname + " (" + item.cardnumber + ") <small>" + item.dateofbirth + " " + item.address + " " + item.city + " " + item.zipcode + " " + item.country + "</small></a>" ) koha-tmpl/intranet-tmpl/prog/en/includes/circ-patron-search-results.inc: <td><a href="[% data_url | url %]">[% borrower.surname | html %], [% borrower.firstname | html %]</a></td> koha-tmpl/intranet-tmpl/prog/en/modules/members/moremember-print.tt: <title>Summary for [% patron.firstname | html %] [% patron.surname | html %] ([% patron.cardnumber | html %])</title> koha-tmpl/intranet-tmpl/prog/en/modules/members/paycollect.tt: <a href="/cgi-bin/koha/members/pay.pl?borrowernumber=[% patron.borrowernumber | uri %]">Pay fines for [% patron.firstname | html %] [% patron.surname | html %]</a> &rsaquo; and many, many more. -- You are receiving this mail because: You are watching all bug changes.

1 5