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

[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 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 21846] New: Using emoji as tags doesn't discriminate between emoji when calculating weights or searching
by bugzilla-daemon＠bugs.koha-community.org 13 Jun '19

13 Jun '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21846 Bug ID: 21846 Summary: Using emoji as tags doesn't discriminate between emoji when calculating weights or searching Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 58

[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 22489] New: Onboarding tool fails due to inserting maxissueqty into IssuingRule
by bugzilla-daemon＠bugs.koha-community.org 12 Jun '19

12 Jun '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22489 Bug ID: 22489 Summary: Onboarding tool fails due to inserting maxissueqty into IssuingRule Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Installation and upgrade (web-based installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: hayleymapley(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Target Milestone: --- When going through the onboarding process, the tool fails on submit of Step 5 - creating an issuing rule. This is due to the maxissueqty column having been removed from the IssuingRules table and added to the CirculationRules table but redundant code still exists in onboarding.pl. As you can see below the maxissueqty variable is being added to the params hash which is used to make the new issuing rule. if ( $step == 5 ) { if ( $op eq 'add_validate_circ_rule' ) { #If no libraries exist then set the $branch value to * my $branch = $input->param('branch') || '*'; my $type = $input->param('type'); my $branchcode = $input->param('branch'); my $categorycode = $input->param('categorycode'); my $itemtype = $input->param('itemtype'); my $maxissueqty = $input->param('maxissueqty'); my $issuelength = $input->param('issuelength'); my $lengthunit = $input->param('lengthunit'); my $renewalsallowed = $input->param('renewalsallowed'); my $renewalperiod = $input->param('renewalperiod'); my $onshelfholds = $input->param('onshelfholds') || 0; $maxissueqty =~ s/\s//g; $maxissueqty = undef if $maxissueqty !~ /^\d+/; $issuelength = $issuelength eq q{} ? undef : $issuelength; my $params = { branchcode => $branchcode, categorycode => $categorycode, itemtype => $itemtype, maxissueqty => $maxissueqty, renewalsallowed => $renewalsallowed, renewalperiod => $renewalperiod, issuelength => $issuelength, lengthunit => $lengthunit, onshelfholds => $onshelfholds, }; my $issuingrule = Koha::IssuingRule->new($params); eval { $issuingrule->store; }; -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 33

[Bug 22099] New: "List requests" button displays when listing requests
by bugzilla-daemon＠bugs.koha-community.org 11 Jun '19

11 Jun '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22099 Bug ID: 22099 Summary: "List requests" button displays when listing requests Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew.isherwood(a)ptfs-europe.com Target Milestone: --- On the main ILL Requests page that lists all requests ("illlist" action), the "List request" button is displayed, which makes no sense since we're already listing requests. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[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 21973] New: CAS URL escaped twice, preventing login
by bugzilla-daemon＠bugs.koha-community.org 10 Jun '19

10 Jun '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21973 Bug ID: 21973 Summary: CAS URL escaped twice, preventing login Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: stefan.berndtsson(a)ub.gu.se QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org Bug 21526 applies the "url" filter on the CAS login link despite it being escaped already in C4/Auth_with_cas.pm, resulting in a double escape and a non-functioning login via CAS. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[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