March 2019 - Koha-bugs - lists.koha-community.org

[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 22339] New: Elasticsearch - fixed field mappings should match MARC ranges
by bugzilla-daemon＠bugs.koha-community.org 24 May '19

24 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22339 Bug ID: 22339 Summary: Elasticsearch - fixed field mappings should match MARC ranges 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 Target Milestone: --- ff7-00 is set to: 007_/1 it should be mapped to position 0 I believe any other specific character positions should be checked to ensure they are corect as well To recreate: 1 - Find an item with an 007 in your catalog 2 - Make sure it is indexed in ES 3 - View the ES record: kohadevbox curl 'localhost:9200/koha_kohadev_biblios/data/19?pretty=yes' | grep -A7 ff7 koha testing docker curl 'es:9200/koha_kohadev_biblios/data/19?pretty=yes' | grep -A7 ff7 adjust for other setups 4 - Note the 00 indexes the 01 position, etc -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19

[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 21964] New: Switch two-column templates to Bootstrap grid: Patrons part 2
by bugzilla-daemon＠bugs.koha-community.org 23 May '19

23 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21964 Bug ID: 21964 Summary: Switch two-column templates to Bootstrap grid: Patrons part 2 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: testopia(a)bugs.koha-community.org Blocks: 20654 These two-column patron templates can be updated to use the Bootstrap grid. - modules/members/maninvoice.tt - modules/members/member-flags.tt - modules/members/member-password.tt - modules/members/member.tt - modules/members/memberentrygen.tt Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20654 [Bug 20654] Omnibus: Update two-column templates to use Bootstrap grid -- You are receiving this mail because: You are watching all bug changes.

1 16

[Bug 22461] New: Regression in #20287: LDAP user replication broken with mapped extended patron attributes
by bugzilla-daemon＠bugs.koha-community.org 22 May '19

22 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22461 Bug ID: 22461 Summary: Regression in #20287: LDAP user replication broken with mapped extended patron attributes Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: oliver.behnke(a)aei.mpg.de QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Reproduce: 1) Use LDAP authentication with user replication 2) Add a field mapping for an extended patron attribute (e.g. MYATTRIB) 3) Try to log in for the first time (new Koha user) 4) Error: "opac-user.pl: DBIx::Class::Row::store_column(): No such column 'MYATTRIB' on Koha::Schema::Result::Borrower at /usr/share/koha/lib/Koha/Object.pm line 75" Presumed cause: Commit [1] changed the way new patrons are created during LDAP replication (first login). The previous implementation (C4::Members::AddMember) took into account extended patron attributes by filtering them out before instantiating the new patron DB object [2]. The current implementation lacks this vital step. I chose a severity of critical because after upgrading from 18.05 to 18.11 no new users are able to log in anymore. Cheers [1] https://github.com/Koha-Community/Koha/commit/a6059c4d2d43e43aa021069ce97d6… [2] https://github.com/Koha-Community/Koha/blob/1b13c453e20e47c5e25bd946b50dd38… -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 36

[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 22184] New: Move payment note out of payments table and into payment form
by bugzilla-daemon＠bugs.koha-community.org 21 May '19

21 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22184 Bug ID: 22184 Summary: Move payment note out of payments table and into payment form Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- >From Comment 14 on Bug 21918: I got confused about the payment note feature. I am wondering, do we need it to be on the payments table? It seems a little confusing as you seem to only be able to save it actually paying a fine. Wouldn't it be enough if the field appeared editable on the actual form? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[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