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

[Bug 21477] New: Use of REMOTE_ADDR causes problems when Koha is behind a proxy
by bugzilla-daemon＠bugs.koha-community.org 13 Jun '19

13 Jun '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21477 Bug ID: 21477 Summary: Use of REMOTE_ADDR causes problems when Koha is behind a proxy 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org For sysprefs like: RestrictedPageLocalIP we check the REMOTE_ADDR to get the IP, for setups behind a proxy we have seen issues as the IP is not matching the users IP. We should have a support for checking X_FORWARDED_FOR in order to check the IP of the end user -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 19598] New: ES configuration - Make the columns sortable/searchable
by bugzilla-daemon＠bugs.koha-community.org 13 Jun '19

13 Jun '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19598 Bug ID: 19598 Summary: ES configuration - Make the columns sortable/searchable Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: severine.queune(a)bulac.fr It would be great if we could sort (even search ?) the columns of the 3 tabs of Elastic search configuration (page koha/admin/searchengine/elasticsearch/mappings.pl). That would make the configuration easier. I would also be very useful to use different sorts/searches to check which fields are facetable / which subfields of XXX marc block are mapped / etc. to make the configuration more trustworthy. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 20830] New: Make sure a fund is selected when ordering from staged file
by bugzilla-daemon＠bugs.koha-community.org 11 Jun '19

11 Jun '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20830 Bug ID: 20830 Summary: Make sure a fund is selected when ordering from staged file Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org When selecting orders from a staged file, we should check that a fund is set. - We only want to check entries that have been selected for order (checkbox) - We only want to complain, when the fund entry on the selected entry is empty and there is also no default fund set on the accounting details tab -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 26

[Bug 17407] New: Fields cataloged using MARC21 880 are only searchable using keyword search
by bugzilla-daemon＠bugs.koha-community.org 10 Jun '19

10 Jun '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17407 Bug ID: 17407 Summary: Fields cataloged using MARC21 880 are only searchable using keyword search Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org According to http://www.loc.gov/marc/bibliographic/bd880.html, the MARC21 880 field is used to store versions of other MARC21 fields that have a different representation than the main cataloged fields. This would be used, for instance, to hold title or author information not stored in a Latin character set. The 880 field is then linked back to 245 (Title), 100 (author), etc, via 880$6. The $6 subfield follows the linkage rules here: http://www.loc.gov/marc/bibliographic/ecbdcntf.html under '$6 - Linkage'. ... the linkage fields are used to give context -- which field / occurrence is being linked to, which language / is being used, and whether the script is written right-to-left or left-to-right. -- Without this development, titles cataloged using 880 fields can be searched using keyword searches, but searches using the linked title, author, subject are not searchable using title, author, subject searches. This will be an issue for both Zebra and Elastic search. -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 17400] New: KOHA keeps requesting log-in
by bugzilla-daemon＠bugs.koha-community.org 08 Jun '19

08 Jun '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17400 Bug ID: 17400 Summary: KOHA keeps requesting log-in Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbiggs(a)washoecounty.us QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com KOHA keeps requesting log-in information every time I start a new transaction. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 21422] New: Create logging for any action triggered by a staff override
by bugzilla-daemon＠bugs.koha-community.org 08 Jun '19

08 Jun '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21422 Bug ID: 21422 Summary: Create logging for any action triggered by a staff override Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com E.g. log checkouts overridden by AgeRestrictionOverride AllFinesNeedOverride AllowFineOverride AllowNotForLoanOverride AllowRenewalLimitOverride AllowTooManyOverride or holds overridden by AllowHoldPolicyOverride -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 20671] New: Adding "surname" to instructions. import_borrowers.pl / import_borrowers.tt
by bugzilla-daemon＠bugs.koha-community.org 07 Jun '19

07 Jun '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20671 Bug ID: 20671 Summary: Adding "surname" to instructions. import_borrowers.pl / import_borrowers.tt Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: jesse(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org It appears that surname is now a required field when importing a file with patron data. According to the instructions, however, only 'branchcode' and 'categorycode' are required. Latter should be amended if surname is now required as well. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 18377] New: Add Plack/PSGI file for dev install
by bugzilla-daemon＠bugs.koha-community.org 07 Jun '19

07 Jun '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18377 Bug ID: 18377 Summary: Add Plack/PSGI file for dev install 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 Koha lacks a proper Plack file for dev install. debian/templates/plack.psgi is for package install and misc/plack/koha.psgi seems a bit outdated (you need 2 plack servers running — 1 for opac and 1 for intranet — and the REST API is not enabled in it) I'll attach a new one, based on debian/templates/plack.psgi but suited for a dev install -- You are receiving this mail because: You are watching all bug changes.

1 16

[Bug 16733] New: Adjust or make flexible some paths in debian scripts
by bugzilla-daemon＠bugs.koha-community.org 07 Jun '19

07 Jun '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16733 Bug ID: 16733 Summary: Adjust or make flexible some paths in debian scripts Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Packaging Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: mirko(a)abunchofthings.net -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 66

[Bug 18003] New: Should deletedborrowers.borrowernumber be a primary key?
by bugzilla-daemon＠bugs.koha-community.org 07 Jun '19

07 Jun '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18003 Bug ID: 18003 Summary: Should deletedborrowers.borrowernumber be a primary key? Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 17782 (Raised from bug 17782) DBIC needs a primary key to work correctly. We could be tempt to make borrowernumber a primary key, but a use case could bring thing. Indeed if a table is empty and the mysql (mariadb behaves identically) server restarted, the Auto Increment (AI) is reset. Problematic use case: 1. Install Koha 2. Create a patron (borrowers.borrowernumber = 1) 3. Delete it (deletedborrowers.borrowernumer = 1, and AI is set to 2 4. Restart mysql => borrowers is empty so AI is reset 5. Create a patron (borrowers.borrowernumber = 1) 6. Delete it => We will try to insert a new row with an existing borrowernumber (1) into the deletedborrowers table: BOOM Solution 1: Do not care about this problematic use case and prevent to delete the last patron. Solution 2: Add a AI primary key (id) to deletedborrowers => The 2 tables borrowers and deletedborrowers will differ, bugs will be expected Solution 3: Deal with that at code level: when a patron is created, guess the borrowernumber it will get and check if it does not already exist in the deletedborrowers table. If so, force it before inserting it Solution 4: Do not enforce this constraint at DB level but set the primary key to DBIC schema: Koha::Schema::Result::Deletedborrower: __PACKAGE__->set_primary_key("borrowernumber"); Problem: Koha::Database->new->schema->resultset('Deletedborrower')->find(42); will raise a warning "DBIx::Class::Storage::DBI::select_single(): Query returned more than one row. SQL that returns multiple rows is DEPRECATED for ->find and ->single" if 42 is duplicated, and the first matching row will be picked Another solution? Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17782 [Bug 17782] Patron updated_on field should be set to current timestamp when borrower is deleted -- You are receiving this mail because: You are watching all bug changes.

1 19