August 2016 - Koha-bugs - lists.koha-community.org

[Bug 15911] New: Use noEnterSubmit CSS class instead of prevent_submit.js
by bugzilla-daemon＠bugs.koha-community.org 19 Mar '19

19 Mar '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15911 Bug ID: 15911 Summary: Use noEnterSubmit CSS class instead of prevent_submit.js Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: jonathan.druart(a)bugs.koha-community.org The JavaScript file prevent_submit.js seems to be doing the same work that the .noEnterSubmit CSS class does via staff-global.js. If so, the extra file should be removed and the templates modified to work with staff-global.js. -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 16817] New: Apply hold fee on collection not application
by bugzilla-daemon＠bugs.koha-community.org 17 Mar '19

17 Mar '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16817 Bug ID: 16817 Summary: Apply hold fee on collection not application 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: sally.healey(a)cheshiresharedservices.gov.uk QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Patrons are charged for holds as soon as they request an item. We would like patrons to be charged once the item is ready for collection instead. Could this be a system preference? Could the hold fee be applied to the patron's account once the item has been confirmed as ready for collection? Could the generation of the charge be tied to the generation of the Hold Available for Pickup notice? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 15734] New: Audio Alerts issues in master
by bugzilla-daemon＠bugs.koha-community.org 15 Mar '19

15 Mar '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15734 Bug ID: 15734 Summary: Audio Alerts issues in master 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org >From Nick: In master there is a JSON error thrown when AudioAlerts are enabled. When checking in I get: SyntaxError: JSON.parse: expected property name or '}' at line 1 column 3 of the JSON data This does not happen in 3.22 -- You are receiving this mail because: You are watching all bug changes.

1 50

[Bug 16924] New: Add Search by Accelerated Reading Level Range
by bugzilla-daemon＠bugs.koha-community.org 12 Mar '19

12 Mar '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16924 Bug ID: 16924 Summary: Add Search by Accelerated Reading Level Range Change sponsored?: Seeking cosponsors Product: Koha Version: master Hardware: All URL: http://devs.bywatersolutions.com/projects/add-search-a ccelerated-reading-level-range/ OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: nengard(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Work to be done: Create an index for the 526 MARC fields Add range searching to advanced search in OPAC and Staff on new index Seeking Cosponsors here: http://devs.bywatersolutions.com/projects/add-search-accelerated-reading-le… -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 16831] New: Patron List is not generated at the time of filtered search
by bugzilla-daemon＠bugs.koha-community.org 12 Mar '19

12 Mar '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16831 Bug ID: 16831 Summary: Patron List is not generated at the time of filtered search Change sponsored?: --- Product: Koha Version: 16.05 Hardware: All OS: Linux Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: dsamantalis(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Created attachment 52940 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=52940&action=ed… Snapshot at the time searching patron by setting up filters. In the Patron segment when search is carried out by set up filters like patron category, Library etc. no list is generated. But on individual search by patron card number or partial name the patron details is shown.Also when guided report is generated by restricted with category and library branch, generate accurate result. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 16113] New: Specify due date for batch check out
by bugzilla-daemon＠bugs.koha-community.org 05 Mar '19

05 Mar '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16113 Bug ID: 16113 Summary: Specify due date for batch check out Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: marjorie.barry-vila(a)ccsr.qc.ca QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Hi, Currently , we can not manually select a due date in the batch check out tool. This could be a system preference like specifyDueDate or SpecifyReturnDate. Regards, Marjorie -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 15894] New: Unify all account fine payment functions
by bugzilla-daemon＠bugs.koha-community.org 22 Feb '19

22 Feb '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15894 Bug ID: 15894 Summary: Unify all account fine payment functions 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Right now, Koha has four different functions for making payments: recordpayment, makepayment, recordpayment_sellectaccts and makepartialpayment. We should replace these four functions with a single all-singing all-dancing method in the Koha::Namespace. This would help to reduce regressions and make future additions much simpler ( such as my planned re-implementation of account offsets ) and add consistency for logging and whatnot. -- You are receiving this mail because: You are watching all bug changes.

1 34

[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 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 16765] New: Subject links in XSLT detail display do not break into subdivisions
by bugzilla-daemon＠bugs.koha-community.org 12 Feb '19

12 Feb '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16765 Bug ID: 16765 Summary: Subject links in XSLT detail display do not break into subdivisions Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: Boze.1(a)nd.edu QA Contact: testopia(a)bugs.koha-community.org Created attachment 52501 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=52501&action=ed… Illustration of the difference between XSLT and non-XSLT subject links Version: 3.22.04.000 Also tested on older versions and 16.05.00.000 (Catalyst demo site) Using the non-XSLT detail display, subject links are broken up into increasingly detailed subdivisions that can be clicked on. In the attached image, you can see in the first three screen captures that each subject subdivision is a separate link, and creates a search at that level of the subject. It also conveniently provides a tooltip that shows which MARC subfield the subdivision is coming from. The fourth screen capture shows what happens when the XSLT display is in effect. The entire subject with all subfields are treated as a single search. The subfields cannot be searched separately. Note the the same behavior applies to the links for additional authors. It would be great to have the XSLT option work the same way as the non-XSLT option. Settings for screen capture 4 (in attachment) OPACXSLTDetailsDisplay = default TraceSubjectSubdivisions = Include Settings for screen capture 1-3 (in attachment) OPACXSLTDetailsDisplay = (empty, no XSLT) TraceSubjectSubdivisions = Include -- You are receiving this mail because: You are watching all bug changes.

1 2