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

[Bug 17079] New: Umlauts(special chars) are displayed as One Latin-1 char per byte on the plugin-template
by bugzilla-daemon＠bugs.koha-community.org 01 Dec '17

01 Dec '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17079 Bug ID: 17079 Summary: Umlauts(special chars) are displayed as One Latin-1 char per byte on the plugin-template Change sponsored?: --- Product: Koha Version: 16.05 Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: elias.dehler(a)thulb.uni-jena.de QA Contact: testopia(a)bugs.koha-community.org Created attachment 54158 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=54158&action=ed… Searchbar with bug visible The Problem: every character is shown as one latin-1 char per byte Where: On the page which is displayed after the "run tool" action on any plugin (which loads a plugin specific template). Steps to reproduce: - install german language pack (or any language pack with non-standard chars) - install https://github.com/bywatersolutions/koha-plugin-kitchen-sink - pick the action "run tool" - switch language to german (or any language pack with non-standard chars) - The problem is now visible at the search bar (or any other special char displayed) -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 16069] New: XSS issue in basket.pl page
by bugzilla-daemon＠bugs.koha-community.org 28 Nov '17

28 Nov '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16069 Bug ID: 16069 Summary: XSS issue in basket.pl page Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: amitddng135(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com XSS issue in basket.pl page -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 18104] New: allow SIP2 field AE (personal name ) to be customized
by bugzilla-daemon＠bugs.koha-community.org 28 Nov '17

28 Nov '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18104 Bug ID: 18104 Summary: allow SIP2 field AE (personal name ) to be customized Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com Koha's SIP2 server sends the patron's name in the format "Firstname Surname" which is not very good for machine reading. We need to allow the format of the patron name to be customized in a manner similar to what is done with the DA field on bug 16755. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 18

[Bug 16755] New: allow SIP2 field DA ( hold patron name ) to be customized
by bugzilla-daemon＠bugs.koha-community.org 28 Nov '17

28 Nov '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16755 Bug ID: 16755 Summary: allow SIP2 field DA ( hold patron name ) to be customized Change sponsored?: Sponsored Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: SIP2 Assignee: kyle(a)bywatersolutions.com Reporter: nengard(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com, nicole(a)bywatersolutions.com Goal of Development: To allow SIP2 field DA ( hold patron name ) to be customized. Work to be done: 1) Add new parameter da_field_template to SIPConfig.xml 2) Modify C4::SIP::Sip::MsgType::handle_checkin to pass the value of da_field_template to C4::SIP::ILS::Item::hold_patron_name 3) Modify C4::SIP::ILS::Item::hold_patron_name to process the template and output as the patron name if a template is specified -- You are receiving this mail because: You are watching all bug changes.

1 18

[Bug 17039] New: No cancel/new item option when editing an item
by bugzilla-daemon＠bugs.koha-community.org 28 Nov '17

28 Nov '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17039 Bug ID: 17039 Summary: No cancel/new item option when editing an item Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When you have started to edit an item, there is no 'cancel' link and no easy way to catalog a new item instead. -- You are receiving this mail because: You are watching all bug changes.

1 11

[Bug 17969] New: Refactor the way <<items.content>> is generated
by bugzilla-daemon＠bugs.koha-community.org 28 Nov '17

28 Nov '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17969 Bug ID: 17969 Summary: Refactor the way <<items.content>> is generated Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement 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 <<items.content>> is generated 4x in advance_notices.pl and once in overdue_notices.pl It would be better to have it in C4::Letters. It will enforce the fact that it already has the same behavior, make it testable and reusable. -- You are receiving this mail because: You are watching all bug changes.

1 20

[Bug 17176] New: Did you mean searches should respect UseAuthoritiesForTracings and search by terms instead of numbers
by bugzilla-daemon＠bugs.koha-community.org 28 Nov '17

28 Nov '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17176 Bug ID: 17176 Summary: Did you mean searches should respect UseAuthoritiesForTracings and search by terms instead of numbers Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org In catalogs where some authorities may not be linked it would be beneficial to have 'Did you mean?' searches constructed with terms rather than authority numbers as the latter can result in dead links. Alternatively 'Did you mean?' shouldn't suggest unused authorities -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 18357] New: On-site checkouts issues with 'Unlimited'
by bugzilla-daemon＠bugs.koha-community.org 26 Nov '17

26 Nov '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18357 Bug ID: 18357 Summary: On-site checkouts issues with 'Unlimited' 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When on-site checkouts are 'Unlimited' the checkouts can be blocked if there is a limit for checkouts in general To reproduce: Set All/All rule with Unlimited/unlimited for normal/onsite checkouts Will be able to perform onsite checkout Edit rule to be 15/Unlimited normal/onsite Will get error 'Too many: 1 on site checkout, only are allowed' Set rule to 15/15 Onsite checkouts work again Similar issue with Default checkout, hold and return policy and Default checkout limit by patron category -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 18131] New: Matching staged records when using elastic search fails
by bugzilla-daemon＠bugs.koha-community.org 26 Nov '17

26 Nov '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18131 Bug ID: 18131 Summary: Matching staged records when using elastic search fails Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: stefan.berndtsson(a)ub.gu.se QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl There is a perl related bug in C4/Matcher.pm when collecting matched records. "simple_search_compat" returns a reference to an array of matches. When using ElasticSearch, this array contains MARC::Record objects. The score for these matches are then collected (currently line 692-694) into a hash "%matches" where the matched object is used as the key. Perl converts all hash keys into strings, so the object is lost. The hash "%matches" is used in a foreach (line 708) where it assumes the object can be recovered from the key, but this is not the case. The error in the log is: stage-marc-import.pl: Can't locate object method "fields" via package "MARC::Record=HASH(0xb403da8)" (perhaps you forgot to load "MARC::Record=HASH(0xb403da8)"?) at /home/vagrant/kohaclone/C4/Biblio.pm line 2691., referer: http://localhost:8081/cgi-bin/koha/tools/stage-marc-import.pl Steps to reproduce (given an instance using ElasticSearch as search engine): 1. Export a bibliographic record in MARC format. 2. Create a matching rule that matches on "999$c" with a score and threshold of 1000 (doesn't really matter as long as they're the same) 3. Edit the record in Koha so that they're slightly different (this is probably unnecessary). 4. Upload the exported file in Stage MARC import, and select the matching rule you created, then click on "Stage for import". Expected outcome: Redirected to the batch page with the matching record being shown. Actual outcome: Things seem to hang, but in reality the staging has crashed with the error shown above. -- You are receiving this mail because: You are watching all bug changes.

1 26

[Bug 17051] New: Default order biblio subfields in framework
by bugzilla-daemon＠bugs.koha-community.org 25 Nov '17

25 Nov '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17051 Bug ID: 17051 Summary: Default order biblio subfields in framework Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: marjorie.barry-vila(a)ccsr.qc.ca QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Hi, It would be nice if subfields in framework editor could have subfields put in any order. With RDA, subfield "i" is often in first position. It would be nice having a way to set by default an order of subfield for a framework. Regards, Marjorie -- You are receiving this mail because: You are watching all bug changes.

1 3