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

[Bug 8137] Checkout limit for all libraries
by bugzilla-daemon＠bugs.koha-community.org 01 Aug '24

01 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8137 Thibaud Guillot <thibaud.guillot(a)biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #169727|0 |1 is obsolete| | --- Comment #120 from Thibaud Guillot <thibaud.guillot(a)biblibre.com> --- Created attachment 169927 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=169927&action=e… Bug 8137: Add 'global checkout limits' table The aim here is to avoid the accumulation of checkouts possibilities through the rules of the various branches, in order to have a global quota. Test plan: 1) Apply this patch 2) Run updatedatabase script and rebuild schema, restart_all.. 3) On circulation rules page you will find a new table "Global checkout limits". 4) If you enter values, they will overwrite the existing values, creating limits for all branches combined. 5) Test it by set a "current checkouts allowed" to 2 on "standard rules section" and set a "global" maxissueqty to 1. Normally 1 is the new limit for now. 6) You can also add a "current checkouts allowed" on other branches and see that you can't accumulate checkouts (you can also delete "global" values and see that if you have 3 on a branch and 2 on other, you can perform 5 checkouts in total. 7) Note that on specific branch circulation rules page the table cannot be modified, but just shown as a reminder. If main matrix is empty on specific branch the table is hidden by default (cause if none values it's referred to standard rules). Sponsored-by: BibLibre -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8137] Checkout limit for all libraries
by bugzilla-daemon＠bugs.koha-community.org 01 Aug '24

01 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8137 Thibaud Guillot <thibaud.guillot(a)biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|In Discussion |Needs Signoff -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 37164] New: worker-output.log file grows to incredible sizes and causing the server to crash
by bugzilla-daemon＠bugs.koha-community.org 01 Aug '24

01 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37164 Bug ID: 37164 Summary: worker-output.log file grows to incredible sizes and causing the server to crash Change sponsored?: --- Product: Koha Version: 23.05 Hardware: All OS: Linux Status: NEW Severity: critical Priority: P5 - low Component: bugs.koha-community.org Assignee: koha-bugs(a)lists.koha-community.org Reporter: yuriy.kotsyuk(a)oa.edu.ua QA Contact: testopia(a)bugs.koha-community.org Created attachment 168002 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=168002&action=e… scrinchot worker-output.log.2 (fragment) The worker-output.log file grows to incredible sizes. While checking one of the files (5 GB), a warning entry was found and this entry was duplicated a huge number of times over a short period of time. The first two records are as follows: DBIx::Class::Storage::DBI::catch {...} (): DBI Connection failed: DBI connect('database=koha_library;host=localhost;port=3306','koha_library',...) failed: Lost connection to MySQL server at 'reading initial communication packet', system error: 104 at /usr/share/koha/lib/Koha/Database.pm line 91. at /usr/share/koha/lib/Koha/Objects.pm line 312 DBIx::Class::Storage::DBI::catch {...} (): DBI Connection failed: DBI connect('database=koha_library;host=localhost;port=3306','koha_library',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) at /usr/share/koha/lib/Koha/Database.pm line 91. at /usr/share/koha/lib/Koha/Objects.pm line 312 Line number three indicates the date and time 2024/05/20 17:35:52 In general, the record looks like this: [2024/05/20 17:35:52] [WARN] Frame not processed - malformed JSON string, neither tag, array, object, number, string or atom, at character offset 0 (before "You must log in usin...") at /usr/share/koha/bin/workers/background_jobs_worker.pl line 120. main::catch {...} /usr/share/koha/bin/workers/background_jobs_worker.pl (122) This entry occurs 985 times in a row. Recording in the next second: [2024/05/20 17:35:53] [WARN] Frame not processed - malformed JSON string, neither tag, array, object, number, string or atom, at character offset 0 (before "You must log in usin...") at /usr/share/koha/bin/workers/background_jobs_worker.pl line 120. main::catch {...} /usr/share/koha/bin/workers/background_jobs_worker.pl (122) occurs 1483 times in a row. Recording in the next second: [2024/05/20 17:35:54] [WARN] Frame not processed - malformed JSON string, neither tag, array, object, number, string or atom, at character offset 0 (before "You must log in usin...") at /usr/share/koha/bin/workers/background_jobs_worker.pl line 120. main::catch {...} /usr/share/koha/bin/workers/background_jobs_worker.pl (122) occurs 6952 times A total of 16,709,173 messages of the same type were generated from 2024/05/20 17:35:52 to 2024/05/21 10:59:08 After this series of messages, other messages have already appeared: Cannot connect to the message broker, the jobs will be processed anyway (Failed to connect: Error connecting to localhost:61613: Connection refused at /usr/share/perl5/Net/Stomp.pm line 27.; giving up at /usr/share/perl5/Net/Stomp.pm line 27. ) at /usr/share/koha/bin/workers/background_jobs_worker.pl line 92. Cannot connect to the message broker, the jobs will be processed anyway (Failed to connect: Error connecting to localhost:61613: Connection refused at /usr/share/perl5/Net/Stomp.pm line 27.; giving up at /usr/share/perl5/Net/Stomp.pm line 27. ) at /usr/share/koha/bin/workers/background_jobs_worker.pl line 92. Today, worker-output.log was 108 GB in size and took up all free disk space, causing the server to crash. Perhaps someone had the same problems and was able to overcome them -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 37458] New: opacusercss
by bugzilla-daemon＠bugs.koha-community.org 01 Aug '24

01 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37458 Bug ID: 37458 Summary: opacusercss Change sponsored?: --- Product: Koha Version: 24.05 Hardware: All OS: Linux Status: NEW Severity: critical Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: lvargassarmiento(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 169511 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=169511&action=e… cada rato me sale el mismo error y tengo que cerrar todo y volver a entrar y sigue apareciendo el mismo error Cuando trato de colocar codigos en el Opacusercss me sale este error solo cuando presiono los cambioas para guardarlo. TypeError: Cannot read properties of undefined (reading 'map') -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 37541] New: Changing PIN after turning on forced PIN reset results in setting of NEVER
by bugzilla-daemon＠bugs.koha-community.org 31 Jul '24

31 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37541 Bug ID: 37541 Summary: Changing PIN after turning on forced PIN reset results in setting of NEVER Change sponsored?: --- Product: Koha Version: 23.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: chanel.wheeler(a)yavapaiaz.gov QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org We set up a new patron category with an expiration date of 90 days. We then moved the shared staff accounts over to this new category and set a manual expiration date of a few weeks out. We then went into one of these staff accounts and manually changed the PIN. Now on the patron detail page, it shows their PIN Expires as NEVER. It should show either the manual expiration date we'd already set, or a new date 90 days out. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 13722] Titles with articles not sorting correctly in lists
by bugzilla-daemon＠bugs.koha-community.org 31 Jul '24

31 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13722 Lauren Denny <lauren_denny(a)sil.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lauren_denny(a)sil.org -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 10060] Allow adding a branch parameter to the web-based self check to indicate library its used at
by bugzilla-daemon＠bugs.koha-community.org 31 Jul '24

31 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10060 Chris Rowlands <chris.rowlands6(a)nhs.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |chris.rowlands6(a)nhs.net -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8425] Autobarcode generates duplicate barcodes with AcqCreateItems = on order
by bugzilla-daemon＠bugs.koha-community.org 31 Jul '24

31 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8425 --- Comment #16 from Baptiste Wojtkowski (bwoj) <baptiste.wojtkowski(a)biblibre.com> --- Note: this should also resolve: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30056 -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8425] Autobarcode generates duplicate barcodes with AcqCreateItems = on order
by bugzilla-daemon＠bugs.koha-community.org 31 Jul '24

31 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8425 Baptiste Wojtkowski (bwoj) <baptiste.wojtkowski(a)biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|koha-bugs(a)lists.koha-commun |baptiste.wojtkowski@biblibr |ity.org |e.com CC| |baptiste.wojtkowski@biblibr | |e.com --- Comment #15 from Baptiste Wojtkowski (bwoj) <baptiste.wojtkowski(a)biblibre.com> --- Note, the proposed approach does not solve any problem of concurrent accesses to barcode.pl but I do not think it could be resolved without refactoring barcode.pl. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 8425] Autobarcode generates duplicate barcodes with AcqCreateItems = on order
by bugzilla-daemon＠bugs.koha-community.org 31 Jul '24

31 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8425 --- Comment #14 from Baptiste Wojtkowski (bwoj) <baptiste.wojtkowski(a)biblibre.com> --- Created attachment 169884 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=169884&action=e… Bug 8425: Increment the barcode on each call of set_barcode() Duplicate barcodes are generated when placing an Order in Acquisitions when AcqCreateItem = "placing an order" and Autobarcode is turned on. The problem is that you can accidentally attach 3 items to an order, but only 1 will be saved to the database. When you go to receive your order, you can only receive 1 item as the other two were never made, since the barcode wasn't unique. In 3.8.0, a software error comes up which prevent any item creation, I believe, but master (3.9.x) doesn't throw any warnings or errors. Yes.. This tries and solve a bug from 3.8.0 /o/ Test plan: 1 - set syspref "autoBarcode" to generated in the form <branchcode> yymm001 2 - set the barcode field to "barcode.pl" in marc structure 3 - create a new basket 4 - add one item to this basket 5 - click on the barcode field -> it should have a barcode 6 - click on add item and click on the new barcode fiels, it should have the same value APPLY PATCH: 7 - click on the barcode field -> it should have a barcode 8 - click on add item and click on the new barcode fields, it should have an higher barcode. Note : The barcode is incremented each time the barcode with an empty value is clicked on and only on "hbyymmincr" mode. Therefore, if the librarian removes the value from barcode and click again, they could get another barcode. I do not know if it is an issue. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0