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

[Bug 17045] New: Write API to Allow instant use of reports library
by bugzilla-daemon＠bugs.koha-community.org 21 Feb '19

21 Feb '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17045 Bug ID: 17045 Summary: Write API to Allow instant use of reports library Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: gmcharlt(a)gmail.com Reporter: lisetteslatah(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Write an API that would allow us to select and run reports directly from the Koha Community Reports Library, as discussed at Koha US Conference 2016 during the reports Round table. -- You are receiving this mail because: You are watching all bug changes.

1 6

[Bug 18383] New: items.onloan schema comment seems to be incorrect.
by bugzilla-daemon＠bugs.koha-community.org 19 Feb '19

19 Feb '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18383 Bug ID: 18383 Summary: items.onloan schema comment seems to be incorrect. Change sponsored?: --- Product: Koha Version: 16.11 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Database Assignee: gmcharlt(a)gmail.com Reporter: pongtawat(a)punsarn.asia QA Contact: testopia(a)bugs.koha-community.org Currently the items.onloan schema comment (in SQL and hence on schema.koha-community.org too) is like this: defines if item is checked out (NULL for not checked out, and checkout date for checked out) However, on my installation (16.11.06), the date that Koha put into items.onloan column seems to be due date. So, probably the comment should be changed to: defines if item is checked out (NULL for not checked out, and due date for checked out) -- You are receiving this mail because: You are watching all bug changes.

1 12

[Bug 19731] New: Notify when you add new item with reservations
by bugzilla-daemon＠bugs.koha-community.org 19 Feb '19

19 Feb '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19731 Bug ID: 19731 Summary: Notify when you add new item with reservations 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: patrick.robitaille(a)collecto.ca QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Hi, It would be nice in Koha when you add a new item to have a notification or a pop-uo when all the items for this record are on loan and there are reservations for this record. That could be usefull to have this notification for the person who has added the new item to be niticed that it should be put on hold to satisfy reservations and not shelved with available status. Patrick. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 16714] New: Unexpected logout with "IP address change"
by bugzilla-daemon＠bugs.koha-community.org 16 Feb '19

16 Feb '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16714 Bug ID: 16714 Summary: Unexpected logout with "IP address change" Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: normal 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 I get a new issue (not sure since when) under Plack: I am logged out with "IP address change" just after the first login. To reproduce: - logout - restart plack - login - click somewhere => You will be logged out I have tried to debug: diff --git a/C4/Auth.pm b/C4/Auth.pm index 985bd39..a494ddf 100644 --- a/C4/Auth.pm +++ b/C4/Auth.pm @@ -818,6 +818,9 @@ sub checkauth { $userid = $s_userid; $sessiontype = $session->param('sessiontype') || ''; } + + warn $ip; + warn $ENV{REMOTE_ADDR}; if ( ( $query->param('koha_login_context') && ( $q_userid ne $s_userid ) ) || ( $cas && $query->param('ticket') && !C4::Context->userenv->{'id'} ) || ( $shib && $shib_login && !$logout && !C4::Context->userenv->{'id'} ) I get: After the login: $ip=undef, $ENV{REMOTE_ADDR}=192.168.254.1 After the click producing the logout: $ip=192.168.254.1, $ENV{REMOTE_ADDR}=127.0.0.1 After the second login: $ip=127.0.0.1, $ENV{REMOTE_ADDR}=127.0.0.1 -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 19701] New: Modify patron loses password in Microsoft Edge
by bugzilla-daemon＠bugs.koha-community.org 15 Feb '19

15 Feb '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19701 Bug ID: 19701 Summary: Modify patron loses password in Microsoft Edge Change sponsored?: --- Product: Koha Version: 16.05 Hardware: PC OS: Windows Status: NEW Severity: minor Priority: P5 - low Component: Browser compatibility Assignee: oleonard(a)myacpl.org Reporter: emma.perks(a)heartofengland.nhs.uk QA Contact: testopia(a)bugs.koha-community.org In Microsoft Edge editing a patron record takes away the password and you have to add it back in before you can save the record. -- You are receiving this mail because: You are watching all bug changes.

1 6

[Bug 19816] New: output_pref must raised an exception if called with dateformat => rfc3339 and > dateonly => 1
by bugzilla-daemon＠bugs.koha-community.org 15 Feb '19

15 Feb '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19816 Bug ID: 19816 Summary: output_pref must raised an exception if called with dateformat => rfc3339 and > dateonly => 1 Change sponsored?: --- Product: Koha Version: unspecified 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: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 18330 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18330 [Bug 18330] REST API: Date-time handling -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 24

[Bug 18039] New: Move the mandatory and optional files for non-english languages into ' default' directory so bug 17855 permits use of other languages
by bugzilla-daemon＠bugs.koha-community.org 15 Feb '19

15 Feb '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18039 Bug ID: 18039 Summary: Move the mandatory and optional files for non-english languages into 'default' directory so bug 17855 permits use of other languages Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: All Status: ASSIGNED 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 Depends on: 17855 At the moment after applying bug 17855 (updated web installer and onboarding tool) users can only use Koha in English. This bug requires the moving of mandatory and optional files into default directories for all other non-English languages. The rationale for placing the work for this in a bug separate to bug 17855 is that it is going to take a lot of testing to confirm all files have been moved and Koha with the updated web installer and onboarding tool works with other languages. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17855 [Bug 17855] Updated Koha web installer and new onboarding tool feature to guide users through setting up Koha -- You are receiving this mail because: You are watching all bug changes.

1 39

[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 19572] New: opac-result item avaibility not the same as opac-detail shows
by bugzilla-daemon＠bugs.koha-community.org 14 Feb '19

14 Feb '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19572 Bug ID: 19572 Summary: opac-result item avaibility not the same as opac-detail shows Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: david.bourgault(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org This is an issue two of our clients have encountered : the item avaibility in the result page does not match the one in the detail page. e.g.: The items have a notforloan value of -2, which is mapped through Authorised_Values to "In Processing" (or equivalent) but on the OPAC result page, it is displayed as "On Order". The detailed page show the correct value. >From my analysis, this is because whereas the intranet results and the opac details use the database to get items statuses, the opac result goes through the XSLT processing, and doesn't have access to the Authorised_Values table. This is worked around by some hardcoded values in the "item namespace" created by XSLT.pm. It's possible to fix this issue case-by-case for each client, but that's a very ugly solution. I don't plan to submit a patch to this bug, because I am not sure how to solve the issue. (If my explanations are unclear please tell me) -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 17683] New: OPAC_SEARCH_LIMIT no longer accepts group codes as limits
by bugzilla-daemon＠bugs.koha-community.org 14 Feb '19

14 Feb '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17683 Bug ID: 17683 Summary: OPAC_SEARCH_LIMIT no longer accepts group codes as limits Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Keywords: rel_3_16_candidate Severity: trivial Priority: P4 Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gitbot(a)bugs.koha-community.org, gmcharlt(a)gmail.com, paul.poulain(a)biblibre.com Depends on: 10798 SetEnvIf Host "opac2.your-domain.com" OPAC_SEARCH_LIMIT=branch:search_group_code This worked up until recently :( Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10798 [Bug 10798] OPAC_SEARCH_LIMIT behaves badly with search groups -- You are receiving this mail because: You are watching all bug changes.

1 5