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

[Bug 42087] New: Add dependency File::LibMagic for validating file using magic numbers
by bugzilla-daemon＠bugs.koha-community.org 29 Jun '26

29 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42087 Bug ID: 42087 Summary: Add dependency File::LibMagic for validating file using magic numbers Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Packaging Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: mtj(a)kohaaloha.com There are many cases in Koha where we're working with files and we want to know what type of file it is, but we can't trust the file extension or the Content-Type that it's uploaded with, because those are user-controlled data. A common method for testing file type is using magic numbers via the libmagic library. In Perl File::LibMagic provides Perl bindings to this C library, which makes it easy to check what kind of file we're working with (to a reasonable degree). libfile-libmagic-perl is available in Debian, so it should be an easy dependency to add. It will help improve our security and even just user experience. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 22

[Bug 40911] New: SIP Patron->new() generates ORM warnings with undefined/empty patron_id
by bugzilla-daemon＠bugs.koha-community.org 28 Jun '26

28 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40911 Bug ID: 40911 Summary: SIP Patron->new() generates ORM warnings with undefined/empty patron_id Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Noticed in production, when C4::SIP::ILS::Patron->new is passed a $patron_id that is not defined or empty -or any processing makes it like that- (e.g. faulty plugins, malformed SIP requests) logs get flooded with DBIx::Class errors and Perl warnings when it should never reach the ORM with a query because there's nothing to search for. Similar to bug 40910 for Item->new(), the Patron constructor should validate input early and return gracefully without generating warnings for undefined/empty patron identifiers. Expected behavior: Silent return for invalid input, proper debug logging for troubleshooting Actual behavior: Warning spam in SIP server logs, potential DBIx::Class constraint errors This affects SIP server stability and makes log analysis difficult due to noise from invalid requests. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 21214] New: cleanup_database.pl --mail should let admin choose which letter codes to keep
by bugzilla-daemon＠bugs.koha-community.org 28 Jun '26

28 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21214 Bug ID: 21214 Summary: cleanup_database.pl --mail should let admin choose which letter codes to keep Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: charles.farmer(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz We are often asked if an email was sent to a patron, and despite not having 100% confirmation that the message reached the person, it feels bad when fines are attached to it and no information's left in the database for our librarians. A new patch would let certain messages stay in the database, despite their age, based on their letter_code. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 50

[Bug 36303] New: Add after_circ_action hook action for checking in item that was not checked out
by bugzilla-daemon＠bugs.koha-community.org 28 Jun '26

28 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36303 Bug ID: 36303 Summary: Add after_circ_action hook action for checking in item that was not checked out Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Plugin architecture Assignee: koha-bugs(a)lists.koha-community.org Reporter: glasklas(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org This patch adds an after_circ_action hook action for the case when an item that is not checked out is checked in. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 12

[Bug 13666] Allow SIP2 checkin/checkout to get branch from institution_id field AO
by bugzilla-daemon＠bugs.koha-community.org 28 Jun '26

28 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13666 --- Comment #14 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- Benjamin, I know Deichman is no longer using Koha - should we reset assignee? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 13666] Allow SIP2 checkin/checkout to get branch from institution_id field AO
by bugzilla-daemon＠bugs.koha-community.org 28 Jun '26

28 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13666 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs Signoff |Failed QA --- Comment #13 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- I uploaded a patch that fixes the QA script issues (patch description, tidiness), but we will still need to do some additional things: 1) As it stands this would be a hidden feature as the flag isn't documented outside the code snippet where it's added. It should probably be in the SIPconfig.xml example file at least and with the SIP config in the GUI now maybe somewhere else too. 2) We'll need unit tests for the change to C4/SIP/Sip/MsgType.pm. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 13666] Allow SIP2 checkin/checkout to get branch from institution_id field AO
by bugzilla-daemon＠bugs.koha-community.org 28 Jun '26

28 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13666 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #187144|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 13666] Allow SIP2 checkin/checkout to get branch from institution_id field AO
by bugzilla-daemon＠bugs.koha-community.org 28 Jun '26

28 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13666 --- Comment #12 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- Created attachment 201122 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=201122&action=e… Bug 13666: Allow SIP2 checkin/checkout to get branch from institution_id field AO This patch adds a policy flag in SIPConfig.xml that allows overriding branch on SIP2 checkout with the AO (institution id) field. Since SIP2 also uses C4::Context this patch has to modify C4::Context->userenv->{'branch'} Test plan: 1) Either use telnet or apply patch from bug #13159 to use sip command line client 2) Checkout book with SIP2 using a modified institution id (field AO) than the one defined in SIPConfig.xml for the account 3) Notice returned AO is still same as in SIPConfig account 4) Also notice checkout history in admin gives same 'checked out from' 5) Apply this patch and add 'allow_branch_override="true" to the policy of your ILS 6) Restart SIP server 7) Repeat 2) 8) Notice that 3) and 4) now reports the modified institution id -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 39023] New: Add utf8 output to CSV output of overdue_notices.pl
by bugzilla-daemon＠bugs.koha-community.org 28 Jun '26

28 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39023 Bug ID: 39023 Summary: Add utf8 output to CSV output of overdue_notices.pl Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: davewood(a)gmx.at QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz the misc/cronjobs/overdue_notices.pl script produces output/files with confusing encoding apparently depending on the content of the lines written. sometimes with characters encoded in latin1 or utf8 in the same file. https://github.com/Koha-Community/Koha/blob/main/misc/cronjobs/overdue_noti… ``` - open $csv_fh, ">", $csvfilename or die "unable to open $csvfilename: $!"; + open $csv_fh, ">:encoding(UTF-8)", $csvfilename or die "unable to open $csvfilename: $!"; ``` there is possible more needed to fix this then just changing this one line. ``` overdue_notices.pl -v -test -list-all -date="2024-11-01" -csv="overdue.csv" -library="AT-LBST" ``` # examples # ASCII text (only csv headers present) # ISO-8859 text (if german umlauts are present) # Non-ISO extended-ASCII text (if german umlauts AND "č" present) ``` ls 202501*|xargs file 20250101_0310_overdue_test.csv: ASCII text 20250102_0310_overdue_test.csv: ASCII text 20250103_0310_overdue_test.csv: ISO-8859 text 20250104_0310_overdue_test.csv: ASCII text 20250105_0310_overdue_test.csv: ASCII text 20250106_0310_overdue_test.csv: ASCII text 20250107_0310_overdue_test.csv: ISO-8859 text 20250108_0310_overdue_test.csv: ISO-8859 text, with very long lines 20250109_0310_overdue_test.csv: Non-ISO extended-ASCII text, with very long lines 20250110_0310_overdue_test.csv: Non-ISO extended-ASCII text 20250111_0310_overdue_test.csv: ASCII text 20250112_0310_overdue_test.csv: ASCII text 20250113_0310_overdue_test.csv: ISO-8859 text 20250114_0310_overdue_test.csv: Non-ISO extended-ASCII text, with very long lines 20250115_0310_overdue_test.csv: ISO-8859 text, with very long lines 20250116_0310_overdue_test.csv: ISO-8859 text 20250117_0310_overdue_test.csv: ISO-8859 text 20250118_0310_overdue_test.csv: ASCII text 20250119_0310_overdue_test.csv: ASCII text 20250120_0310_overdue_test.csv: ISO-8859 text 20250121_0310_overdue_test.csv: ISO-8859 text 20250122_0310_overdue_test.csv: ISO-8859 text 20250123_0310_overdue_test.csv: ISO-8859 text 20250124_0310_overdue_test.csv: Non-ISO extended-ASCII text, with very long lines 20250125_0310_overdue_test.csv: ASCII text 20250126_0310_overdue_test.csv: ASCII text 20250127_0310_overdue_test.csv: Non-ISO extended-ASCII text 20250128_0310_overdue_test.csv: ISO-8859 text 20250129_0310_overdue_test.csv: ASCII text 20250130_0310_overdue_test.csv: ASCII text 20250131_0310_overdue_test.csv: Non-ISO extended-ASCII text, with very long lines ``` old bugs of the same kind in overdue_notices.pl https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8687 https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26601 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 40813] New: Add ability to embed page start and end timing
by bugzilla-daemon＠bugs.koha-community.org 28 Jun '26

28 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40813 Bug ID: 40813 Summary: Add ability to embed page start and end timing Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org It would be useful to know what time a page load was initiated and rendering completed for debugging purposes. The most reasonable solution I've found is to get a time from the start of get_template_and_user and the end of intranet-bottom.inc. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 34