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

[Bug 17724] New: Callnumber not copied into serial issue, when callnumber subfield is linked to a plugin
by bugzilla-daemon＠bugs.koha-community.org 06 May '22

06 May '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17724 Bug ID: 17724 Summary: Callnumber not copied into serial issue, when callnumber subfield is linked to a plugin Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com To test: - Make sure your 952$o (callnumber) is linked to a plugin such as cn_browser.pl in your frameworks - Create a subscription with "create item on receive" and a callnumber - Receive an issue - Verify that the callnumber is not copied into the item on receive - Remove the plugin from the framework - Verify that the callnumber now is copied into the item on receive -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 29212] New: Use Flatpickr on OPAC pages
by bugzilla-daemon＠bugs.koha-community.org 06 May '22

06 May '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29212 Bug ID: 29212 Summary: Use Flatpickr on OPAC pages 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: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: testopia(a)bugs.koha-community.org Depends on: 28982 There are few instances of the jQueryUI datepicker in the OPAC templates which should be replaced with Flatpickr. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28982 [Bug 28982] Use Flatpickr on onboarding pages -- You are receiving this mail because: You are watching all bug changes.

1 46

[Bug 26305] New: Warn IE users of Staff Interface that it is no longer supported and to use a support browser instead
by bugzilla-daemon＠bugs.koha-community.org 06 May '22

06 May '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26305 Bug ID: 26305 Summary: Warn IE users of Staff Interface that it is no longer supported and to use a support browser instead Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Browser compatibility Assignee: oleonard(a)myacpl.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org I frequently get people raising issues about Koha not working because they're using Internet Explorer. While I think it is very sensible for Koha not to support IE, I think it might be useful in this transitional time to show a warning banner on the Staff Interface to tell users that they can't use IE anymore and expect Koha to work. -- You are receiving this mail because: You are watching all bug changes.

1 22

[Bug 26669] New: Last Run column not updated when report is run publicly (via CoverFlow or elsewhere)
by bugzilla-daemon＠bugs.koha-community.org 05 May '22

05 May '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26669 Bug ID: 26669 Summary: Last Run column not updated when report is run publicly (via CoverFlow or elsewhere) 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: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org Reports show an inaccurate last run date for reports used by CoverFlow. Shouldn't it show that activity, or would coverflow report timestamps bog the system down? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 31

[Bug 26782] New: Circulation conditions: first 2 columns show as sortable, but cannot be sorted
by bugzilla-daemon＠bugs.koha-community.org 05 May '22

05 May '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26782 Bug ID: 26782 Summary: Circulation conditions: first 2 columns show as sortable, but cannot be sorted 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 The first 2 columns for patron category and item type have the little arrow marker, but won't sort when clicked on. -- You are receiving this mail because: You are watching all bug changes.

1 13

[Bug 28190] New: Library limitation column not toggable on itemtypes table
by bugzilla-daemon＠bugs.koha-community.org 05 May '22

05 May '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28190 Bug ID: 28190 Summary: Library limitation column not toggable on itemtypes table Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org The columns_settings.yml section for itemtypes is missing an entry for the 'Parent code' column, and thus some columns are shifted, and it has the effect of preventing the 'Library limitations' column being toggable. -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 26132] New: Improve readability of TooMany
by bugzilla-daemon＠bugs.koha-community.org 05 May '22

05 May '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26132 Bug ID: 26132 Summary: Improve readability of TooMany Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement 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 Depends on: 21946 This is a follow-up of bug 21946. We need to improve the readability of C4::Circulation::TooMany to prevent regressions. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21946 [Bug 21946] Group circulation by item type -- You are receiving this mail because: You are watching all bug changes.

1 40

[Bug 21946] New: Group circulation by item type
by bugzilla-daemon＠bugs.koha-community.org 05 May '22

05 May '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21946 Bug ID: 21946 Summary: Group circulation by item type Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: kyle(a)bywatersolutions.com Reporter: jesse(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Group rules based on item type in order to restrict circulation. In other words, not allow more than x items to be checked out across all media type item types (DVD, VHS, Blue Ray) and not just 4 checkouts per type. Currently patrons can bypass the circulation rules and take out 4 DVDs and 4 VHS and still be within the system limitation but in reality have just taken out 8 media items. This development would allow for the grouping of materials in order to keep that 4 media limit across all types. 1 - Extend the itemtypes table to allow an itemtype to have a parent type 2 - When circulating an item the specific itemtype circulation rules will apply unless unset 3 - For itemtypes with a parent the parent rule will apply when child rule is unset -- You are receiving this mail because: You are watching all bug changes.

1 171

[Bug 25436] New: Google SSO
by bugzilla-daemon＠bugs.koha-community.org 04 May '22

04 May '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25436 Bug ID: 25436 Summary: Google SSO Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: Linux Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: Diwakar.j(a)inspiria.edu.in QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org We would like to single sign in/off through our google g-suite email id. or integration with google directory with Koha users, so we do not need to create users manually. If any one of those possible, kindly share the steps or advise. Regards, Diwakar -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8

[Bug 27078] New: Starman hanging in 3-node Koha cluster when 1 node goes offline.
by bugzilla-daemon＠bugs.koha-community.org 04 May '22

04 May '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27078 Bug ID: 27078 Summary: Starman hanging in 3-node Koha cluster when 1 node goes offline. Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: rcmcdonald91(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org So I've got a pretty interesting case that I've been playing with for the past several weeks. My goal has been to build a converged 3-node Koha cluster. The architecture looks like this: 1. Each node runs the "standalone" Koha stack (Koha, Starman, Apache, ElasticSearch, Memcached, MariaDB). For the sake of example, these nodes are 10.10.100.51, 10.10.100.52, and 10.10.100.53. 2. Galera is used to build the 3-node MariaDB cluster and each Koha node simply talks to the MariaDB server at localhost. This has worked fine and koha is blissfully unaware of the underlying galera cluster. 3. ElasticSearch is built in a 3-node cluster. koha-conf.xml is configured to use all three ES nodes (again at 10.10.100.51, 10.10.100.52, and 10.10.100.53). Again, koha doesn't seem to mind this at all. 4. All three nodes run Memcached and koha-conf.xml is configured to use all three Memcached nodes (again at 10.10.100.51-3). 5. Plack is enabled on all nodes using koha-plack --enable instancename && koha-plack --start instancename. 6. GlusterFS is used to serve up a 3-node replicated volume for /etc/koha/*, /usr/share/koha/*, and /var/lib/koha* across all three nodes. symlinks are used to present this storage in places koha is expecting them to be. Again, this works great. 6. Two HAProxy instances sit in front of these three koha instances (at 10.10.100.2 and 10.10.100.3). koha_trusted_proxies in koha-conf.xml is configured with these two IPs. 7. Finally, HAProxy handles SSL-offloading and client stickiness. This all works fine too. Here is the weirdness... When all three nodes are online, everything is absolutely fine. Everything is snappy, searching works, etc. When I change koha-conf.xml on one node, this is replicated to the other nodes immediately. However, when one node goes offline, the two remaining nodes become really sluggish. I've narrowed this down to a Starman/Plack issue, but I have no idea why. Here's how I arrived at that conclusion. * I started by killing pertinent services one-by-one on Node A. Killing MariaDB on Node A had no effect on Node B and C... though as expected, Node A started spitting out errors that the DB was unavailable. * Next, I stopped Memcached on Node A. Again, this had no effect on Node B and C. * Next, I stopped ElasticSeasrch on Node A. Again, this had no effect on Node B and Node C. * Next, I stopped GlusterFS on Node A. Again, this had no effect on Node B and Node C. * Next, I stopped koha-common on Node A. Again, this had no effect on Node B and Node C. So at this point, Node A is still "online." However, every service related to Koha is stopped (MariaDB, Memcached, ElasticSearch, Apache, koha-common, etc.). As expected, Node B and C keep on working just fine. Here is the weird part, When Node A actually goes offline (i.e. loses network connectivity and/or powers down), Node B and C become very very slow. They still serve traffic, but they are really sluggish. As soon as connectivity is restored to Node A, Node B and Node C speed right back up again. So is this related to Starman/Plack? When I disable Starman/Plack on all nodes, the speed of each node doesn't change when a single node goes offline. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17