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

[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 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 20421] New: Inform staff that patron does have the title checked out during placing hold
by bugzilla-daemon＠bugs.koha-community.org 06 Apr '22

06 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20421 Bug ID: 20421 Summary: Inform staff that patron does have the title checked out during placing hold 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: josef.moravec(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 29

[Bug 22344] New: Limits cannot contain parentheses
by bugzilla-daemon＠bugs.koha-community.org 05 Apr '22

05 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22344 Bug ID: 22344 Summary: Limits cannot contain parentheses 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: dcook(a)prosentient.com.au Target Milestone: --- I've noticed an authorised value of category LOC can't have parentheses in it. If it does, the search silently fails... I'm guessing it doesn't even make it from the ZOOM library in Koha over the connection to Zebra. I'm going to explore in a moment, but people have noticed this and kind of worked around it with #5693 and #7031. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 15750] New: Koha offline circulation Firefox addon does not prompt to clear old entries
by bugzilla-daemon＠bugs.koha-community.org 04 Apr '22

04 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15750 Bug ID: 15750 Summary: Koha offline circulation Firefox addon does not prompt to clear old entries Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: contribs.koha-community.org Assignee: koha-bugs(a)lists.koha-community.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: fridolin.somers(a)biblibre.com, koha-bugs(a)lists.koha-community.org, testopia(a)bugs.koha-community.org If this description is up to date: https://lists.katipo.co.nz/public/koha/2012-May/032825.html ...when I open the KOCT for the first time in a browser session (?) I should be prompted to clear old transactions. I don't find this to be the case. I get no prompt. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes. You are on the CC list for the bug.

1 1

[Bug 17841] New: Can't use indexname "acqdate, st-date-normalized" in keyword search
by bugzilla-daemon＠bugs.koha-community.org 01 Apr '22

01 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17841 Bug ID: 17841 Summary: Can't use indexname "acqdate,st-date-normalized" in keyword search Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org It is possible to search for acquisition date from the advanced search in staff. But if you try to use the index name for an 'expert search' in the keyword search field, no results will come up. Example: Advanced search > acquisition date: 2016-12* (or whatever works for you) This should give correct results. Enter acqdate,st-date-normalized: 2016-12* into the keyword search - no results will appear. Something seems to be missing in order to make it possible to construct the same search manually. -- You are receiving this mail because: You are watching all bug changes.

1 4