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

[Bug 20398] New: Remove search result highlighting
by bugzilla-daemon＠bugs.koha-community.org 20 Apr '22

20 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20398 Bug ID: 20398 Summary: Remove search result highlighting 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: gaetan.boisson(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Search result highlighting is broken and has been broken for a long time: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11270 Adding insult to injury there is no way to deactivate it on the staff interface. We are so used to see it that we don't pay attention, but new users notice it, and complain. It would be good to remove it until it is fixed. (As a general rule i think features that aren't entirely functional shouldn't make it into the release until they are actually ready.) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 57

[Bug 22333] New: Replace duplicated code in CanBookBeRenewed with GetSoonestRenewDate
by bugzilla-daemon＠bugs.koha-community.org 20 Apr '22

20 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22333 Bug ID: 22333 Summary: Replace duplicated code in CanBookBeRenewed with GetSoonestRenewDate 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: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Target Milestone: --- There is some duplicated code between CanBookBeRenewed and GetSoonestRenewDate. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 21682] New: Stock Rotation: Update DB is failing with strict_sql_modes ON
by bugzilla-daemon＠bugs.koha-community.org 19 Apr '22

19 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21682 Bug ID: 21682 Summary: Stock Rotation: Update DB is failing with strict_sql_modes ON Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Database Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org As pointed out in comment 369 in bug 11897 the db update isn't strict modes correct. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 37

[Bug 17018] New: Split AdvancedSearchTypes for staff and OPAC
by bugzilla-daemon＠bugs.koha-community.org 15 Apr '22

15 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17018 Bug ID: 17018 Summary: Split AdvancedSearchTypes for staff and OPAC Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org It would be nice if you could configure AdvancedSearchTypes differently for staff and opac advanced search. -- You are receiving this mail because: You are watching all bug changes.

1 37

[Bug 24103] New: Add option to dump built search query to templates
by bugzilla-daemon＠bugs.koha-community.org 14 Apr '22

14 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24103 Bug ID: 24103 Summary: Add option to dump built search query to templates Change sponsored?: --- Product: Koha Version: master 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org It would be nice to be able to see what is actually being searched in the search engine when performing a query -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 32

[Bug 17720] New: CSRF token is not generated correctly
by bugzilla-daemon＠bugs.koha-community.org 11 Apr '22

11 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17720 Bug ID: 17720 Summary: CSRF token is not generated correctly Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: blocker 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 The CSRF token is not generated correctly if the DB password contain unicode characters. Indeed md5_base64 explodes with Wide character in subroutine entry at /usr/share/perl5/Digest/HMAC.pm line 63. -- You are receiving this mail because: You are watching all bug changes.

1 13

[Bug 17830] New: CSRF token is not generated correctly (bis)
by bugzilla-daemon＠bugs.koha-community.org 11 Apr '22

11 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17830 Bug ID: 17830 Summary: CSRF token is not generated correctly (bis) Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: blocker 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 The same error as bug 17720 can occur if the userid has unicode characters. Wide character in subroutine entry at /usr/share/perl5/Digest/HMAC.pm line 63. -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 22038] New: When exporting account table to excel, decimal is lost
by bugzilla-daemon＠bugs.koha-community.org 08 Apr '22

08 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22038 Bug ID: 22038 Summary: When exporting account table to excel, decimal is lost Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- When you want to export a patron's account lines in Excel, the decimals are lost. So instead of having a fine of 3,75, the Excel file says the fine is 375. Note that I opened the Excel file in LibreOffice Calc. I'm not sure if that affects anything. Although I also opened the file in vim and got the same result: <c r="D2" s="63"><v>375</v></c><c r="E2" s="63"><v>375</v></c> To reproduce: 1) Find a patron with small fines (my patron had 3,75) or create some manual charges 2) In the patrons file, go to the Fines tab and then the Account tab 3) At the top of the account table, click on Excel 4) Open the file 5) Notice the fines are now multiplied by 100 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 25

[Bug 23528] New: Show 'log in to add tags' link on all search result entries
by bugzilla-daemon＠bugs.koha-community.org 08 Apr '22

08 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23528 Bug ID: 23528 Summary: Show 'log in to add tags' link on all search result entries 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Splitting this out as a separate bug report from bug 23210: (In reply to Lucas Gass from comment #0) > If a non-authenticated user goes to the search results page they will only > see the login4tags (Log in to add tags ) text included with the first > result. This should be included with every result. -- You are receiving this mail because: You are watching all bug changes.

1 13

[Bug 23330] New: deleteditemsstocknumberidx should not be a unique index
by bugzilla-daemon＠bugs.koha-community.org 07 Apr '22

07 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23330 Bug ID: 23330 Summary: deleteditemsstocknumberidx should not be a unique index Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Database Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org At the moment, deleteditemsstocknumberidx is a unique index, which means that an item will fail to delete if its "Inventory number" already exists in the deleteditems table. Its counterpart itemsstocknumberidx was renamed to itemstocknumberidx in version 3.03.00.042 (dating from April/May 2011) and made non-unique. I've worked on Koha since early 2012 and only today have I had someone stung by this problem. They've been storing "Copy number" in "Inventory number" for some reason, and it's caught them out. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5