April 2023 - Koha-bugs - lists.koha-community.org

[Bug 21954] New: Koha update having a strange effect on checkout rules
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '23

08 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21954 Bug ID: 21954 Summary: Koha update having a strange effect on checkout rules Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: librarian(a)darwin.cam.ac.uk QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com I have chased a few false trails and was stuck with a checkout error on all items. When checking out books, we kept receiving "No circulation rule is defined for this user and itemtype combination." On checking, all circulation rules were defined as necessary. Rules were in place for both Books and DVDs, for all user categories. We managed to get it to work by placing another rule for 'All' categories, 'All' itemtypes as an overhead. This should never be used following the hierarchy of the rules, but it seems to allow all of the other rules to now be followed (they have become valid). This has a workaround - the all/all rule, but it would be good to know what is going on. It is also good to note that this was working before on 18.05! -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 21988] New: Add SMSSendDriverFromNumber system preference for specifying a source number for SMS messages
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '23

08 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21988 Bug ID: 21988 Summary: Add SMSSendDriverFromNumber system preference for specifying a source number for SMS messages Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew.isherwood(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Some SMS gateways (specifically, in my case, http://123-txt.com) require a "source" number to be specified which all SMS messages appear to be sent from. This bug proposes adding a SMSSendDriverFromNumber syspref, similar to the new EmailSMSSendDriverFromAddress (Bug 20356), to allow a source number to be specified. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 21

[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 27187] New: Cannot delete/update local cover image with LocalCoverImages off
by bugzilla-daemon＠bugs.koha-community.org 06 Oct '23

06 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27187 Bug ID: 27187 Summary: Cannot delete/update local cover image with LocalCoverImages off Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When the LocalCoverImages syspref is set to "Don't display," Koha hides the image itself as well as the Images tab on the bib details page. However, if a library has OPACLocalCoverImages on, they'll likely want to access that Images tab to delete or change the images they're displaying on the OPAC. Could we hide the tab only if *both* sysprefs are off? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 31003] New: WhatsApp notifications
by bugzilla-daemon＠bugs.koha-community.org 05 Oct '23

05 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31003 Bug ID: 31003 Summary: WhatsApp notifications Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org It would be great to support WhatsApp as a delivery medium for notices. https://developers.facebook.com/docs/whatsapp/cloud-api/get-started -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3