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

[Bug 19515] New: Refactor REST API session mocking to reduce ridiculous amounts of duplication
by bugzilla-daemon＠bugs.koha-community.org 19 Jun '19

19 Jun '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19515 Bug ID: 19515 Summary: Refactor REST API session mocking to reduce ridiculous amounts of duplication 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: olli-antti.kivilahti(a)jns.fi The amount of duplication in REST API tests is beyond anything. I must be hallucinating. This adds a t::lib::Mocks::mock_session() which mocks a session reverting to defaults, and checks CGI::Session->flush for errors. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 17978] New: Circ rules will not limit holds
by bugzilla-daemon＠bugs.koha-community.org 19 Jun '19

19 Jun '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17978 Bug ID: 17978 Summary: Circ rules will not limit holds Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com It appears that the holds limit in circ rules is broken. I can set a limit of 0 on holds and it will block the hold, but if I set it to anything higher than 0, it ignores the value altogether and gives the patron unlimited holds. Maxreserves works as expected. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 54

[Bug 19247] New: Feature release change tool
by bugzilla-daemon＠bugs.koha-community.org 19 Jun '19

19 Jun '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19247 Bug ID: 19247 Summary: Feature release change tool Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Installation and upgrade (web-based installer) Assignee: alexbuckley(a)catalyst.net.nz Reporter: alexbuckley(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com -- You are receiving this mail because: You are watching all bug changes.

1 22

[Bug 19530] New: Prevent multiple transfers from existing for one item
by bugzilla-daemon＠bugs.koha-community.org 17 Jun '19

17 Jun '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19530 Bug ID: 19530 Summary: Prevent multiple transfers from existing for one item 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com We have found multiple open branch transfers for a given item. While I'm not sure how it is happening at this point, it seems that it would make sense to cancel any existing branch transfers when initiating a new one. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 33

[Bug 18387] New: 404 errors on page causes SCO user to be logged out
by bugzilla-daemon＠bugs.koha-community.org 14 Jun '19

14 Jun '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18387 Bug ID: 18387 Summary: 404 errors on page causes SCO user to be logged out Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Self checkout Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org If AutoSelfCheck is enabled but there is a 404 error in fetching resources on an SCO page the user is logged out on each request. This is because a 404 also requests the errorpages.tt which is outside the SCO module. This causes a redirect to the opac-auth page when trying to print receipts after completing SCO transaction To recreate: 1 - Enable AuthoSelfCheck prefs 2 - In opacuserjs or scouserjs add a fetch of an unreachable resources 3 - Visit the SCO 4 - Sign in as a patron then click 'finish' 5 - Say 'yes' to receipt 6 - Note you are directed to log in -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 30

[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 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