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

[Bug 24728] New: Short Last Name Search Issue
by bugzilla-daemon＠bugs.koha-community.org 17 Mar '20

17 Mar '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24728 Bug ID: 24728 Summary: Short Last Name Search Issue Change sponsored?: --- Product: Koha Version: 19.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: christofer.zorn(a)ajaxlibrary.ca QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Hello! It was brought to my attention that if a patron has a last name that is two characters long (for example "Lo"), that when you perform a patron search using the top bar, the patron is not found. If you perform the same "filtered" search using "Lo" and "Starts with", results are returned as expected. In our instance, we have between 8 and 10 patrons with the last name "Lo" that do not appear. While I understand that altering the SQL to become shorter will impact what the search results show, there should be away for staff to locate patrons with short names the same way they do for longer names. I'm not sure if this is a legitimate bug or just a limitation, but I wanted to throw this out there and see what comes of it. Thank you! Christofer -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 24730] New: Enhancing hold cancellations
by bugzilla-daemon＠bugs.koha-community.org 16 Mar '20

16 Mar '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24730 Bug ID: 24730 Summary: Enhancing hold cancellations Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Currently, patrons cannot cancel a hold that is triggered (waiting). It would be great if a patron had this ability. Staff currently do, but not the patron. Not sure why this is. It would also be great if there were options for e-mail to staff when a hold has been cancelled, and an alert on the staff home page, along with the suggestion notifications and patron update requests. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 24684] New: Adding text "Address: 1" as circulation note makes field disappear - moremember.pl
by bugzilla-daemon＠bugs.koha-community.org 16 Mar '20

16 Mar '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24684 Bug ID: 24684 Summary: Adding text "Address: 1" as circulation note makes field disappear - moremember.pl Change sponsored?: --- Product: Koha Version: 18.11 Hardware: PC OS: Linux Status: NEW Severity: minor Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: bernard.scaife(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Edit patron record Add the text Address: 1 into the circulation note field Save record Circulation note is not visible. Also, in editing the record, the field is not available to edit. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 24717] New: Koha should set a referrer policy
by bugzilla-daemon＠bugs.koha-community.org 16 Mar '20

16 Mar '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24717 Bug ID: 24717 Summary: Koha should set a referrer policy Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: gmcharlt(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Koha should set a referrer policy [0] to restrict what is passed in the Referer header when external resources (e.g., cover images, added content of various stripes, electronic resources, external images and CSS, etc.) are embedded or navigated to. If a referrer policy is not set, the default policy of no-referrer-when-downgrade means that (say) the full referring URL, which can include record IDs and catalog search strings, will be sent to outside webservers providing external resources provided that loading the external resource doesn't mean downgrading from HTTPS to HTTP. Better values for the referrer policy include: * strict-origin-when-cross-origin * origin-when-cross-origin Values that might break current Koha functionality that inspects the Referer header include: * no-referrer * origin * strict-origin Values that might break legitimate inspection of the Referer header by services that perform referring URL "authentication" include: * no-referrer * same-origin A referrer policy can be set in various ways: - Using a Referrer-Policy HTTP header configured at the Apache or NGINX level - Using a meta tag: <meta name="referrer" content="strict-origin-when-cross-origin"> - Using a referrerpolicy attribute in <a>, <area>, <img>, <iframe>, <script>, or <link> tags - Using a noreferrer link relation in <a>, <area>, or <link> elements. [0] https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referrer-Policy -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 24575] New: Search for locations and collections broken when using ICU
by bugzilla-daemon＠bugs.koha-community.org 15 Mar '20

15 Mar '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24575 Bug ID: 24575 Summary: Search for locations and collections broken when using ICU Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching - Zebra Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de We found a strange bug when using ICU in 17.11 and 18.11 after upgrading from Jessie to Stretch, to be confirmed in later versions: Searching for locations and collections from advanced search in the OPAC/staff client doesn't work using the checkboxes. Redundant quotes are no longer ignored. We found that removing these lines from Search.pm fixes the issue for us: if ( $k !~ /mc-i(tem)?type/ ) { # in case the mc-ccode value has complicating chars like ()'s inside it we wrap in quotes $this_limit =~ tr/"//d; $this_limit = $k.":'".$v."'"; } The patch is backward compatible with Jessie. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 23306] New: fines amount showing zero
by bugzilla-daemon＠bugs.koha-community.org 15 Mar '20

15 Mar '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23306 Bug ID: 23306 Summary: fines amount showing zero Change sponsored?: --- Product: Koha Version: 19.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: sunitabarve(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Created attachment 91480 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=91480&action=ed… circulation of the item does not show fine amount the circulation details of a borrower showing fines amount zero and amount is shown in price. why fines amount is not visible for every borrower. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 24654] New: Trailing double-quote in rda 264 subfield b on opac xslt
by bugzilla-daemon＠bugs.koha-community.org 15 Mar '20

15 Mar '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24654 Bug ID: 24654 Summary: Trailing double-quote in rda 264 subfield b on opac xslt 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 To recreate: 1 - Find or add a recod with a 264 field 2 - Make sure there is a subfield b 3 - View the record in opac 4 - Right click on publisher link and copy and paste into a text editor 5 - Note the trailing " in the search -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 22798] New: Double quote included in Publisher search on tag 264
by bugzilla-daemon＠bugs.koha-community.org 15 Mar '20

15 Mar '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22798 Bug ID: 22798 Summary: Double quote included in Publisher search on tag 264 Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbutosi(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Created attachment 88989 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=88989&action=ed… Field 264 double-quotes On the OPAC, if a user clicks on the hyperlinked Publisher value in the bibliographic record, a double-quote is appended to the search url if the publication value is catalogued in field 264, thus breaking the search. For example: http://library.craigbutosi.ca/cgi-bin/koha/opac-search.pl?q=Provider:Verso%… instead of http://library.craigbutosi.ca/cgi-bin/koha/opac-search.pl?q=Provider:Verso%… The double-quote does not appear in records in which publication data is entered in field 260, thus search succeeds. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 23706] New: Item search CSV export doesn't include collection code
by bugzilla-daemon＠bugs.koha-community.org 15 Mar '20

15 Mar '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23706 Bug ID: 23706 Summary: Item search CSV export doesn't include collection code Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: david.roberts(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com If you do an item search in the staff client and send the output to the screen, the collection column will be populated. However, if you export the same search to CSV, the column is present, but contains no data. After poking around, I found that the screen was outputting items.ccode, whereas the CSV was outputting biblioitems.collectiontitle. Both output formats should use items.ccode. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 18

[Bug 16147] New: OpacItemLocation and not for circulation Item types
by bugzilla-daemon＠bugs.koha-community.org 15 Mar '20

15 Mar '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16147 Bug ID: 16147 Summary: OpacItemLocation and not for circulation Item types Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: ed.veal(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org If you set the OpacItemLocation to anything other than "Call number only" the call number is repeated on the Location line for all items with item types that don't circulate. <xsl:if test="items:itemcallnumber != '' and items:itemcallnumber and $OPACItemLocation='callnum'"> [<span class="LabelCallNumber">Call number: </span><xsl:value-of select="items:itemcallnumber"/>]</xsl:if> <xsl:if test="items:itemcallnumber != '' and items:itemcallnumber"> [<span class="LabelCallNumber">Call number: </span><xsl:value-of select="items:itemcallnumber"/>]</xsl:if> Ed -- You are receiving this mail because: You are watching all bug changes.

1 6