November 2018 - Koha-bugs - lists.koha-community.org

[Bug 21884] New: Writeoff "amount" changed from positive values to negative values.
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '23

08 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21884 Bug ID: 21884 Summary: Writeoff "amount" changed from positive values to negative values. Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: alexanderchen530(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 82653 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=82653&action=ed… Example of pos/neg writeoff values. Hi, This is not a recent issue, I discovered it either after 17.05 or 17.11 update. Before the update, writeoff amounts were displayed in "red positive numbers", but after the update, writeoff amounts became "green negative numbers" just like payments. This is not an issue if it's just humans reading it, but it becomes an issue when doing accounting and stats, when I was totaling fines during a certain time range, positive/negative values cancel each other and provide inaccurate total fine amounts. I used ABS() as a workaround, but I hope it can be fixed globally to keep it uniform. Please see attached pics. Also ticket "#49563: Difference in positive and negative values in writeoff charges" has some discussion as well. I also spoke to Kyle regarding this issue at KohaCon18. Thanks. Alex C -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 21922] New: Allow to decide if price is entered tax inlcuded or excluded on receive
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '23

08 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21922 Bug ID: 21922 Summary: Allow to decide if price is entered tax inlcuded or excluded on receive Change sponsored?: --- Product: Koha Version: 17.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org At the moment the decision if prices entered on receive are inclusive or exclusive taxes is made by settings on vendor level. It would be nice if the list price setting could be overridden on receive to avoid having to do those calculations manually. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 21923] New: Sort problem in some letters of Patron list
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '23

08 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21923 Bug ID: 21923 Summary: Sort problem in some letters of Patron list Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: kohadevinim(a)devinim.com.tr QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com While applying patch Bug 21778, we've seen that some Turkish characters on Surname yield incorrect sort order. Ç,İ,Ö,U should come after C,I,O,U. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9

[Bug 21512] New: CalculateFinesOnReturn doesn't work without the syspref finesMode
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '23

08 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21512 Bug ID: 21512 Summary: CalculateFinesOnReturn doesn't work without the syspref finesMode 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: olli-antti.kivilahti(a)helsinki.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Fines are not created for checking in an Item, if the syspref 'CalculateFinesOnReturn' is enabled without the syspref finesMode being in the 'production' -mode (Calculate and charge). CalculateFinesOnReturn must work without the fines.pl -feature. The problem is with the subroutine C4::Circulation::_CalculateAndUpdateFine() Initially it looks like it must be invoked from the fines.pl as well. But that subroutine is only used within the C4::Circulation module for AddRenew and AddReturn. Hence the _CalculateAndUpdateFine() has nothing to do with fines.pl|finesMode. This patch replaces the finesMode-check with CalculateFinesOnReturn-check. I am not sure why there needs to be a specific syspref for the fines.pl, or why CalculateFinesOnReturn is needed, as the fine amounts can be tweaked using the circulation rules matrix and the fines.pl-cronjob can either be ran, or not, with an endless possibility of parameters that shouldn't be in the sysprefs. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 21510] New: Authority search always jumps back to the first search tab no matter what was searched for
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '23

08 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21510 Bug ID: 21510 Summary: Authority search always jumps back to the first search tab no matter what was searched for Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Go to: - Authorities module - Select not the first tab for searching - Search - Notice with reloading the page, search jumps to the first tab -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 21496] New: install.pl: DBD::mysql::st execute failed: Index column size too large. The maximum column size is 767 bytes. at /usr/share/perl5/DBIx/RunSQL.pm line 273.
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '23

08 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21496 Bug ID: 21496 Summary: install.pl: DBD::mysql::st execute failed: Index column size too large. The maximum column size is 767 bytes. at /usr/share/perl5/DBIx/RunSQL.pm line 273. Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: Linux Status: NEW Severity: enhancement Priority: P5 - low Component: Database Assignee: koha-bugs(a)lists.koha-community.org Reporter: migraciones(a)grupoisv.com QA Contact: testopia(a)bugs.koha-community.org Hi, I found the next error when I am installing Koha install.pl: DBD::mysql::st execute failed: Index column size too large. The maximum column size is 767 bytes. at /usr/share/perl5/DBIx/RunSQL.pm line 273. The opertive system is Debian 8 Database is 10.0.32-MariaDB-0+deb8u1 Koha version is Koha 18.05 I need help please Thank you -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 12

[Bug 21452] New: Items available for hold or loan must have an item type
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '23

08 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21452 Bug ID: 21452 Summary: Items available for hold or loan must have an item type Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Because items may be created during cataloging or acquisitions before we know the item type, it's not practical to set a database constraint where items.itype is not NULL. However, if an item without an item type is checked out or a hold is placed on the item, either items.itype or biblioitems.itemtype (if we're using biblio level items) *must* be populated, or we'll trigger an internal server error. We should be checking for this when we set the notforloan status. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 21445] New: Report - having two date ranges in query creates a formatting issue when running report
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '23

08 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21445 Bug ID: 21445 Summary: Report - having two date ranges in query creates a formatting issue when running report Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: tgoatley(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org When the report is run like the following query, the second half of the second date range does not display. SELECT borrowers.cardnumber, borrowers.surname, borrowers.firstname, borrowers.dateofbirth, borrowers.dateenrolled FROM borrowers WHERE dateofbirth BETWEEN <<Date of Birth BETWEEN (yyyy-mm-dd)|date>> AND << AND (yyyy-mm-dd)|date>> AND dateenrolled BETWEEN <<Enrollment Date BETWEEN (yyyy-mm-dd)|date>> AND <<and (yyyy-mm-dd)|date>> AND branchcode=<<Branch|branches>> ORDER BY borrowers.surname ASC Reformatting the query as follows all dates ranges display correctly. SELECT borrowers.cardnumber, borrowers.surname, borrowers.firstname, borrowers.dateofbirth, borrowers.dateenrolled FROM borrowers WHERE dateofbirth BETWEEN <<Date of Birth BETWEEN (yyyy-mm-dd)|date>> AND << AND (yyyy-mm-dd)|date>> AND dateenrolled BETWEEN <<Enrollment Date BETWEEN (yyyy-mm-dd)|date>> AND <<and (yyyy-mm-dd)|date>> AND branchcode=<<Branch|branches>> ORDER BY borrowers.surname ASC -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 21414] New: view_borrower_infos_from_any_libraries can't be used with IndependentBranches
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '23

08 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21414 Bug ID: 21414 Summary: view_borrower_infos_from_any_libraries can't be used with IndependentBranches Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: severine.queune(a)bulac.fr QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When IndependentBranches is turned on, library filter on 'Patrons' menu page ('cgi-bin/koha/members/members-home.pl') only allows the current user site. In spite of the use of the 'view_borrower_infos_from_any_libraries permission', it's not possible to search for patrons from other libraries, even if we're part of the same group of libraries. We can access patron account using the url. No modifications are allowed whether we set IndependentBranchesPatronModifications to 'yes' or 'no'. See also Bug 12599 - IndependentBranches Holes -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 17868] New: Improve display of authors in cart and list emails
by bugzilla-daemon＠bugs.koha-community.org 05 Oct '23

05 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17868 Bug ID: 17868 Summary: Improve display of authors in cart and list emails Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Lists 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 The cart and list emails display a lot of subfields for the author. Example: Author: Seemann, Christian --Bearb. --adp $a $e $4 It would be nice to not display $4 (relator code) if there is $e (relator term). -- You are receiving this mail because: You are watching all bug changes.

1 2