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

[Bug 21544] New: Self Check-in tool does not trigger holds
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '23

08 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21544 Bug ID: 21544 Summary: Self Check-in tool does not trigger holds Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Bug 15492 Stand alone self Check-in Tool has been released into 18.05, however, if a book that has a hold on it gets returned through the stand alone self checkin tool, the hold does not trigger. There is no alert to the patron that this book needs to be brought to the circulation desk or prompt for any other direction. For libraries to use this self checkin tool, there needs to be some function/block that alerts the checkin with a hold to be different than a book with no hold. I tested, both bib level holds and item level holds were treated the same way, with no alert. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 21561] New: Check out restriction to category / branch
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '23

08 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21561 Bug ID: 21561 Summary: Check out restriction to category / branch Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: joseanjos(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com As discussed here: http://koha.1045719.n5.nabble.com/Check-out-restriction-to-category-branch-… its not possible to restrict holds between one library to a group of libraries. With independentbraches it will restrict everything, including Patrons modification. IndependentBranchesPatronModifications should prevent that but doesn't do it. The pretended is this: 1 Main Library (City hall Library CHL) 20 School Libraries (on the same server) Assuming that if a Patron from a School wants to be patron of CHL it will be duplicated Shouldn't be possible checkout from CHL to any school Patron Shouldn't be possible checkout from school to any CHL Patron Should be possible to transfer from CHL to any school Patron and vice-versa School Staff category should be able to modify Patrons because: - Every student is created with is student Nº - On next year he can change from school - Librarian from school should be able to change Library from Student This last point is very important! Otherwise only super librarians can change it. That would be impossible to manage because hundreds of students change every year. The Librarian of each school MUST do that job. Something like Library transfer limits but Library Holds limits would be nice -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 21609] New: Store pre-rendered html in search engine (zebra or elastic).
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '23

08 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21609 Bug ID: 21609 Summary: Store pre-rendered html in search engine (zebra or elastic). Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org XSLT rendering is slow, I started to think about whether it would be possible to store pre-rendered HTML in zebra or elastic, so that we only have to run the marcxml to html xslt transformations at indexing time rather than per, search. It's a time vs. space optimization, and I don't know if the html generated by xslt ever gets cached; if it does, we might not see any benefit. Anyway, putting it out for discussion. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 21642] New: create patron card template in koha generate error not assign template id
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '23

08 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21642 Bug ID: 21642 Summary: create patron card template in koha generate error not assign template id Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: Linux Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: it.officer(a)ppsu.ac.in QA Contact: testopia(a)bugs.koha-community.org create patron card template in koha generate error not assign template id -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 21677] New: MARC detail view may show field header info erroneously
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '23

08 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21677 Bug ID: 21677 Summary: MARC detail view may show field header info erroneously 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: pasi.kallinen(a)joensuu.fi QA Contact: testopia(a)bugs.koha-community.org If the fields in the marcxml are not in order, and LabelMARCView is set to compact, the MARC detail view can show the field headers multiple times. To reproduce: 1) Turn on LabelMARCView 2) Turn on EnableAdvancedCatalogingEditor (Rancor allows entering fields in any order, unlike the old editor) 3) Catalogue a new record with the following fields in this order: 655 _ _ ‡afoo 100 _ _ ‡abar 655 _ _ ‡abaz 650 _ _ ‡aqwerty 655 _ _ ‡aqux 655 _ _ ‡aquux 4) Go to that record's MARC detail view. In the 6xx tab, you will see three separate entries for 655 fields: 655 $a foo 655 $a baz 655 $a qux $a quux How it should look: 655 $a foo $a baz $a qux $a quux -- You are receiving this mail because: You are watching all bug changes.

1 6

[Bug 21707] New: Wrong CSRF token - adding a new patron with auto generated card number turned on
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '23

08 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21707 Bug ID: 21707 Summary: Wrong CSRF token - adding a new patron with auto generated card number turned on Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: cfhong2000(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Trying to add a new patron by entering Surname and click Save. Card Number leave blank since it is using auto-generated. The following error was thrown. Software error: Wrong CSRF token at /usr/share/koha/intranet/cgi-bin/members/memberentry.pl line 307. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[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