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

[Bug 21031] New: Apache Rewrite rules don't work for API when using anything but Debian package Plack configuration
by bugzilla-daemon＠bugs.koha-community.org 14 Feb '19

14 Feb '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21031 Bug ID: 21031 Summary: Apache Rewrite rules don't work for API when using anything but Debian package Plack configuration Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: REST api Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au If you install Koha using the Debian packages and you enable Plack, you should be able to reach the API using the following URL: "/api/v1/" If you install Koha using the Debian packages and you don't enable Plack (or you install from source or you're using a git install or whatever else), you can only get the same API response by visiting "/api/v1/app.pl/api/v1/spec" It appears to me that the Rewrite rules in etc/koha-httpd.conf, debian/templates/apache-shared-opac.conf, and debian/templates/apache-shared-intranet.conf don't work. Fixing this doesn't seem quite as easy as just copying over the Apache configuration for Plack-enabled instances, unfortunately, but I'm looking at this... -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 26

[Bug 18175] New: Makefile sets koha-httpd api path incorrectly for standard installs
by bugzilla-daemon＠bugs.koha-community.org 14 Feb '19

14 Feb '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18175 Bug ID: 18175 Summary: Makefile sets koha-httpd api path incorrectly for standard installs Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: alex.sassmannshausen(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org When performing a standard (or single) install, Makefile.PL generates an koha-httpd.conf with a hardcoded ../api/$1/app.pl reference. This error causes all REST api routes to fail in a standard/single install context. GET fails with 404, PUT fails with 403. The hard-coded path is correct in the dev context. Switching from an Apache variable to a Makefile variable, and hence replacing the hardcoded ../api bit of the path should fix this. Alex -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 11

[Bug 13515] Table messages is missing FK constraints and is never cleaned up
by bugzilla-daemon＠bugs.koha-community.org 14 Feb '19

14 Feb '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13515 Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Failed QA |Signed Off -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 13515] Table messages is missing FK constraints and is never cleaned up
by bugzilla-daemon＠bugs.koha-community.org 14 Feb '19

14 Feb '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13515 --- Comment #12 from Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> --- Created attachment 85138 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=85138&action=ed… Bug 13515: Fix contrainst name before deleting it -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14610] Add ability to place article requests in Koha
by bugzilla-daemon＠bugs.koha-community.org 14 Feb '19

14 Feb '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14610 Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |22068 -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 3820] Members in Log Viewer Showing ?? in UPDATE
by bugzilla-daemon＠bugs.koha-community.org 14 Feb '19

14 Feb '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=3820 Petr Havel <pe.havel(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pe.havel(a)gmail.com -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 12532] Redirect guarantee email to guarantor
by bugzilla-daemon＠bugs.koha-community.org 14 Feb '19

14 Feb '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12532 --- Comment #69 from Mikaël Olangcay Brisebois <mikael.olangcay-brisebois(a)inLibro.com> --- Created attachment 85135 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=85135&action=ed… Bug 12532 - (follow up) clean up -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 12532] Redirect guarantee email to guarantor
by bugzilla-daemon＠bugs.koha-community.org 14 Feb '19

14 Feb '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12532 Mikaël Olangcay Brisebois <mikael.olangcay-brisebois(a)inLibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #80313|0 |1 is obsolete| | --- Comment #68 from Mikaël Olangcay Brisebois <mikael.olangcay-brisebois(a)inLibro.com> --- Created attachment 85134 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=85134&action=ed… Bug 12532 - Send emails to guarantee and guarantor Checks for the syspref "RedirectGuaranteeEmail" in Koha::Patrons::notice_email_address. When enabled, emails to a patron with a guarantor will be sent to both guarantor and guarantee. It does not affect values in the message_queue table. Test plan: Before applying 1) Search, or create, a patron with guarantor 2) Enable checkout emails 3) Checkout an item. An email should be sent only to the guarantee 4) Apply this patch 5) Run updatedatabase.pl 6) Enable 'RedirectGuaranteeEmail' 7) Go through step 1) to 3). Email should now be sent to both. 8) Run t/db_dependant/Members.t Sponsored by: Ville de Victoriaville -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 22229] New: Elasticsearch - fields do not have aliases - Koha should always use the common term internally
by bugzilla-daemon＠bugs.koha-community.org 14 Feb '19

14 Feb '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22229 Bug ID: 22229 Summary: Elasticsearch - fields do not have aliases - Koha should always use the common term internally 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: nick(a)bywatersolutions.com Target Milestone: --- This problem was discovered in the advanced search - when limiting by shelving location the search is composed as limit=mc-loc:{term} this fails in ES because the index is setup as 'location' What works in both is: limit=location:{term} We either need to build field aliases into ES (https://www.elastic.co/guide/en/elasticsearch/reference/master/alias.html) Or make sure to use consistent names across Koha -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 13044] Deprecate old book drop mode
by bugzilla-daemon＠bugs.koha-community.org 14 Feb '19

14 Feb '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13044 --- Comment #12 from Benjamin Daeuber <bdaeuber(a)cityoffargo.com> --- (In reply to Kyle M Hall from comment #10) > Specifically, it makes sense to allow a patron to pay up to the current > amount owed in fees and fines. For if a patron owes $5 on a closed fine, and > $3 on an accruing fine, the patron should be able to pay $8 right now with > the $5 fine being paid off and $3 in credit staying on the account. That way > the account balance is 0 and when that item is returned the credit will be > automatically used to pay some or all of the balance of the fine. I think this would work well and solve several issue. The one proviso is that a method of dealing with credits would need to be a part of this. Right now you need to create a manual invoice to offset a credit and that's already a hassle. A "pay credit" option that allows you to pay out the credit to the patron would be necessary. -- You are receiving this mail because: You are watching all bug changes.

1 0