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

[Bug 23164] New: Add a way to unmock preferences and config entries
by bugzilla-daemon＠bugs.koha-community.org 27 Jan '21

27 Jan '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23164 Bug ID: 23164 Summary: Add a way to unmock preferences and config entries Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- There should be a way to unmock mocked things. In my opinion t::lib::Mocks should be object-oriented, and keep references to the context object that is used for mocking. -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 24643] New: Koha::DateUtils::dt_from_string rfc3339 cannot handle high precision seconds
by bugzilla-daemon＠bugs.koha-community.org 27 Jan '21

27 Jan '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24643 Bug ID: 24643 Summary: Koha::DateUtils::dt_from_string rfc3339 cannot handle high precision seconds Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew.isherwood(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org The RFC3339 spec (https://www.ietf.org/rfc/rfc3339.txt) says that the second component of a date/time can contain fractions of a second, e.g. 2011-10-05T14:48:00.000Z This is the format returned by Javascript's toISOString() function. Unfortunately, when dt_from_string encounters a string in this format, it effectively drops the time component entirely and you end up with: 2011-10-05T00:00:00Z The problem lies in the regex that attempts to match the string when dt_from_string is called with the 'rfc3339' parameter. Adding support for optional fractions is straightforward. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 21

[Bug 25898] New: Prohibit indirect object notation
by bugzilla-daemon＠bugs.koha-community.org 27 Jan '21

27 Jan '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25898 Bug ID: 25898 Summary: Prohibit indirect object notation Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: julian.maurice(a)biblibre.com Reporter: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Indirect object notation is when you write: my $cgi = new CGI; Recently announced Perl 7 (https://www.perl.com/article/announcing-perl-7/) will disable this notation by default. We should write instead: my $cgi = CGI->new Perl 7 does not have a release date yet, but it's better to be prepared :) This bug is for adding a rule in .perlcriticrc and removing all indirect object notations. -- You are receiving this mail because: You are watching all bug changes.

1 35

[Bug 17168] New: Add a command line script for updating patron category based on status
by bugzilla-daemon＠bugs.koha-community.org 27 Jan '21

27 Jan '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17168 Bug ID: 17168 Summary: Add a command line script for updating patron category based on status Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: gmcharlt(a)gmail.com Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Work to be done: * Create a script to run on a regular basis that updates patrons from one category to another based on parameters passed in as defined below * checks fine amount * checks registration date * checks patron fields for specific value -- You are receiving this mail because: You are watching all bug changes.

1 92

[Bug 22345] New: when i type localhost in the browser i get this error Software error: mkdir /var/cache/koha/sunlibrary/templates//usr: Permission denied at /usr/lib/i386-linux-gnu/perl5/5.22/Template/Provider.pm line 388.
by bugzilla-daemon＠bugs.koha-community.org 27 Jan '21

27 Jan '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22345 Bug ID: 22345 Summary: when i type localhost in the browser i get this error Software error: mkdir /var/cache/koha/sunlibrary/templates//usr: Permission denied at /usr/lib/i386-linux-gnu/perl5/5.22/Template/Provider.p m line 388. Change sponsored?: --- Product: Project Infrastructure Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hea Assignee: chris(a)bigballofwax.co.nz Reporter: sadiark88(a)gmail.com QA Contact: jonathan.druart(a)bugs.koha-community.org Target Milestone: --- -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 25265] New: Elasticsearch - Batch editing items on a biblio can lead to incorrect index
by bugzilla-daemon＠bugs.koha-community.org 27 Jan '21

27 Jan '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25265 Bug ID: 25265 Summary: Elasticsearch - Batch editing items on a biblio can lead to incorrect index 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 TO recreate: 1 - Have a bib with several items, none marked 'not for loan' 2 - Do a staff search that returns this biblio 3 - Items show as available 4 - Click on title to go to details page 5 - Edit->Item in a batch 6 - Set the not for loan status for all items 7 - Repeat your search 8 - Some items show as not-for-loan, some show as available -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 95

[Bug 27097] New: Make Koha version number and date of update more obvious
by bugzilla-daemon＠bugs.koha-community.org 27 Jan '21

27 Jan '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27097 Bug ID: 27097 Summary: Make Koha version number and date of update more obvious Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: barbara.johnson(a)bedfordtx.gov QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com We know what version of Koha we are using by looking at the 'About Koha' button from the staff home page. But it's less obvious to us when the monthly maintenance releases are installed by our support vendor. It would be helpful if the version number and install date of the the release was displayed on the Koha staff home page. One thought is to display this info in the lower right hand side of the home page. Another option might be to send an automated email to the KohaAdminEmailAddress so that staff is more aware of these updates. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8

[Bug 23939] New: Title missing from Checked out box
by bugzilla-daemon＠bugs.koha-community.org 26 Jan '21

26 Jan '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23939 Bug ID: 23939 Summary: Title missing from Checked out box Change sponsored?: --- Product: Koha Version: 19.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com In 19.05, the small checked-out box (circulation.tt) that usually displays the title, barcode and due date (as a quick look at what the library is checking out to the patron), SEE SCREENSHOT. This is now only showing barcode and date due. Can we resolve and get the title to display again. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 26525] New: Changing pickup location for multiple holds with transfer limits enforced only passes one bib
by bugzilla-daemon＠bugs.koha-community.org 26 Jan '21

26 Jan '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26525 Bug ID: 26525 Summary: Changing pickup location for multiple holds with transfer limits enforced only passes one bib Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: bwsdonna(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com When changing the pickup location during the process of placing multiple bibs on hold when branch transfer limits are enforced, the page reloads and only the first bib record is passed. 1. Set sys pre Use Branch Transfer Limits to Enforce 2. Search for titles in staff interface 3. From results screen, select 2 or more bibs and click place hold button 4. Choose a different pickup location from the hold screen 5. Only 1 bib number is passed, removing the other bibs This occurs whether using the cart or from the results list. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 26676] New: Add a way to see details on past cash-ups
by bugzilla-daemon＠bugs.koha-community.org 26 Jan '21

26 Jan '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26676 Bug ID: 26676 Summary: Add a way to see details on past cash-ups 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org At the moment when we do multiple cashups, there is no overview page to see the past ones. We can only see a bit of information on the last cash-ups. It would be nice to have a way to list cashups for a timeframe for audit and other purposes. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2