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

[Bug 21457] New: datelastseen and datelastborrowed out of sync
by bugzilla-daemon＠bugs.koha-community.org 26 May '19

26 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21457 Bug ID: 21457 Summary: datelastseen and datelastborrowed out of sync 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: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com In the items table we have these two columns: - datelastborrowed - the date the item was last checked out/issued - datelastseen - the date the item was last see (usually the last time the barcode was scanned or inventory was done) Based on these descriptions you would expect that datelastseen was always the same as or more recent than datelastborrowed, right? One of our customer libraries just made me aware that this is not always the case. This SQL finds the unexpected data: SELECT COUNT(*) FROM items WHERE datelastborrowed > datelastseen; Three of our sites have this unexpected data. They all use SIP2. But we also have a couple sites that use SIP2 that do *not* have unexpected data, so that might be a false lead. Anyone else seen this? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 21589] New: Series link formed from 830 field is incorrect
by bugzilla-daemon＠bugs.koha-community.org 24 May '19

24 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21589 Bug ID: 21589 Summary: Series link formed from 830 field is incorrect 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Bug 13692 corrected the series link for records using a 490/800 combination When a record has a 490/830 conbination for series, the link is malformed (title is used as author, title is blank) -- You are receiving this mail because: You are watching all bug changes.

1 25

[Bug 20692] New: koha-plack doesn't check for Include *-plack.conf line in /etc/apache2/sites-available/$ISNTANCE.conf
by bugzilla-daemon＠bugs.koha-community.org 24 May '19

24 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20692 Bug ID: 20692 Summary: koha-plack doesn't check for Include *-plack.conf line in /etc/apache2/sites-available/$ISNTANCE.conf Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: Linux Status: NEW Severity: minor Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: ropuch(a)bagno.be QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz When enabling Plack, koha-plack uncomment plack related Include in instance's apache conf. Little problem occurs when old pre-plack configs are used, without required Include lines. In this case koha-plack still report success, with no change done. So in the end we have running Plack, but it's doing nothing. plack.log is empty, but there is an entry in plack-error.log that can trick people into thinking they have Plack properly configured and running: 2018/05/01-21:06:27 Starman::Server (type Net::Server::PreFork) starting! pid(10257) Binding to UNIX socket file "/var/run/koha/galway/plack.sock" Setting gid to "1001 1001" Setting uid to "1001" koha-plack:enable_plack() should check if Plack lines exists before trying to uncomment them and either fail with warn message, or add them. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 22

[Bug 19241] New: Items with status of hold show as available in cart
by bugzilla-daemon＠bugs.koha-community.org 24 May '19

24 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19241 Bug ID: 19241 Summary: Items with status of hold show as available in cart Change sponsored?: --- Product: Koha Version: 16.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: michael(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 66784 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=66784&action=ed… attachment shows item with status on hold in cart showing as available Items that have status of on hold show as available on cart list. While users can observe the item has the status of on hold before putting it in the cart, it was reported some patrons find this inconsistency confusing. -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 19302] New: Pass objects to IsAvailableForItemLevelRequest
by bugzilla-daemon＠bugs.koha-community.org 24 May '19

24 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19302 Bug ID: 19302 Summary: Pass objects to IsAvailableForItemLevelRequest 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 Pass Koha::Item and Koha::Patron to C4::Reserves::IsAvailableForItemLevelRequest -- You are receiving this mail because: You are watching all bug changes.

1 30

[Bug 20929] New: koha-dump should not pass a --password argument to mysqldump
by bugzilla-daemon＠bugs.koha-community.org 23 May '19

23 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20929 Bug ID: 20929 Summary: koha-dump should not pass a --password argument to mysqldump Change sponsored?: --- Product: Koha Version: master Hardware: All OS: Linux Status: NEW Severity: minor Priority: P5 - low Component: Packaging Assignee: koha-bugs(a)lists.koha-community.org Reporter: solaris.smoke(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: mirko(a)abunchofthings.net Created attachment 76017 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=76017&action=ed… Use env variable instead of --password argument for mysqldump koha-dump currently passes a password as a CLI argument to mysqldump, which results in the following warning: mysqldump: [Warning] Using a password on the command line interface can be insecure. Depending on how a server is configured, this results in emails being sent to the administrator every time the cron job runs. It's trivial to change this to pass an environment variable instead, so as not to trigger the warning. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 16966] New: Koha:: Patrons - Move GetBorrowersWithIssuesHistoryOlderThan to search_patrons_to_anonymise
by bugzilla-daemon＠bugs.koha-community.org 21 May '19

21 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16966 Bug ID: 16966 Summary: Koha::Patrons - Move GetBorrowersWithIssuesHistoryOlderThan to search_patrons_to_anonymise Change sponsored?: --- Product: Koha Version: master 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: 16961, 16965 Blocks: 16846 The C4::Members::GetBorrowersWithIssuesHistoryOlderThan subroutine is supposed to return the patrons with an issue history older than a given date. It would make more sense to return a list of Koha::Patrons. On the way, the code from AnonymiseIssueHistory will be moved as well to anonymise_issue_history. Note that these 2 subroutines are strongly linked: one is used to know the number of patrons we will anonymise the history, the other one is used to anonymise the issues history. The problem is that the first one is not used to do the action, but only for displayed purpose. In some cases, these 2 values can differ, which could be confusing. Case 1: The logged in librarian is not superlibrarian and IndependentBranches is set: if 2+ patrons from different libraries match the date parameter, the interface will display "Checkout history for 2 patrons will be anonymized", when actually only 1 will be. Case 2: If 2+ patrons match the date parameter but one of them has his privacy set to forever (privacy=0), the same issue will appear. The patches provided will refactor the code and fix these 2 issues. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16846 [Bug 16846] Move patron related code to Koha::Patron https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16961 [Bug 16961] Add the Koha::Objects->update method https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16965 [Bug 16965] Add the Koha::Objects->search_related method -- You are receiving this mail because: You are watching all bug changes.

1 79

[Bug 19781] New: Make a xt test that checks all themes for missing includes, to avoid fallback
by bugzilla-daemon＠bugs.koha-community.org 21 May '19

21 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19781 Bug ID: 19781 Summary: Make a xt test that checks all themes for missing includes, to avoid fallback Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Keywords: Academy Severity: enhancement Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: liz(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org The fallback functionality of the themes is good, but it is resource intensive if something is really really missing from a theme. For example, a user might make a custom theme for their OPAC, specify a TT include, but not include it in their theme (intentionally, or accidentally). The process of looking through all of the themes to find the fallback causes very slow page loads for that page, we should have a test that theme creators can run to check for this circumstance. -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 21547] New: Use update_password in opac-passwd and remove sub goodkey
by bugzilla-daemon＠bugs.koha-community.org 18 May '19

18 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21547 Bug ID: 21547 Summary: Use update_password in opac-passwd and remove sub goodkey Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 28

[Bug 21502] New: Add checks for YAML formatted system preferences to about page
by bugzilla-daemon＠bugs.koha-community.org 18 May '19

18 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21502 Bug ID: 21502 Summary: Add checks for YAML formatted system preferences to about page 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: josef.moravec(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 30