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

[Bug 26198] New: koha-sip --enable should also have --raw_port and --telnet_port options
by bugzilla-daemon＠bugs.koha-community.org 29 Oct '25

29 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26198 Bug ID: 26198 Summary: koha-sip --enable should also have --raw_port and --telnet_port options 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: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com You should be able to provide --raw_port and --telnet_port options to koha-sip --enable, since only 1 Koha instance will be able to use the hard-coded defaults of telnet 8023 and raw 6001. On servers running multiple instances of Koha, you'll want to be able to set up the Koha SIP server with different TCP ports (or the SIP server won't work for those instances). (Note that this isn't an issue if you only run 1 Koha on your server, or if you use 1 Koha per 1 container to provide separate network namespaces.) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 40007] In the Budget section under Acquisition Module - the END DATE must be greater than the START DATE.
by bugzilla-daemon＠bugs.koha-community.org 29 Oct '25

29 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40007 David Cook <dcook(a)prosentient.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Koha |Acquisitions QA Contact| |testopia(a)bugs.koha-communit | |y.org Group|Koha security | Product|Koha security |Koha Assignee|chris(a)bigballofwax.co.nz |koha-bugs(a)lists.koha-commun | |ity.org --- Comment #2 from David Cook <dcook(a)prosentient.com.au> --- Changing this to a normal bug since there's no indication how it's a security bug -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 27557] New: Add the ability to display the error that caused a 500
by bugzilla-daemon＠bugs.koha-community.org 29 Oct '25

29 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27557 Bug ID: 27557 Summary: Add the ability to display the error that caused a 500 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: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 26048 >From bug 26048 comment 19: """ Yesterday I was thinking we could have a syspref to display/hide the error (not the stacktrace). Or enable it by default for superlibrarian. What do you think (on its own bug report of course)? """ >From bug 26048 comment 30: """ But in most production situations I don't think that we'd want to show system generated error messages. It's not a good look. """ Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26048 [Bug 26048] PSGI Koha does not use custom ErrorDocument pages -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 39259] New: SQL reports should allow Common Table Expressions
by bugzilla-daemon＠bugs.koha-community.org 29 Oct '25

29 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39259 Bug ID: 39259 Summary: SQL reports should allow Common Table Expressions Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: schodkowy.omegi-0r(a)icloud.com QA Contact: testopia(a)bugs.koha-community.org Common table expression in MySQL is a syntax like this: WITH cte1 AS (SELECT a, b FROM table1), cte2 AS (SELECT c, d FROM table2) SELECT b, d FROM cte1 JOIN cte2 WHERE cte1.a = cte2.c; However, in Koha/Koha/Report.pm, there's func is_sql_valid: } elsif ( $sql !~ /^\s*SELECT\b\s*/i ) { push @errors, { queryerr => 'Missing SELECT' }; } It should be changed to SELECT|WITH, otherwise it won't allow these nice queries, instead having you to do an ugly workaround like this: SELECT * FROM ( WITH cte1 AS (SELECT a, b FROM table1), cte2 AS (SELECT c, d FROM table2) SELECT b, d FROM cte1 JOIN cte2 WHERE cte1.a = cte2.c ) AS dt; -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 41127] New: Unneeded Permission required when adding child record.
by bugzilla-daemon＠bugs.koha-community.org 28 Oct '25

28 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41127 Bug ID: 41127 Summary: Unneeded Permission required when adding child record. Initiative type: --- Sponsorship --- status: Product: Koha Version: 25.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: esther.melander(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl To replicate: 1. Set EasyAnalyticalRecords to don't show and UseControlNumber to Use. Enable ShowComponentRecords to show in both staff and OPAC. 2. Create a patron with permissions to login into the staff interface. Grant all cataloging permissions except edit_items and edit_items_restricted. 3. Before logging as the example patron, prepare a bibliographic record. Add a child record with an attached item. The title of the child record should be: 245##$aTitle$p1967-1968 4. Login as the example patron. Find the prepared bibliographic child record and click Edit > Edit as new (duplicate). 5. Edit the record so the duplicate child record has a title like: 245##$aTitle$p1968-1969 6. Save. Note the user will be prompted to confirm saving because the system detects the new child record as a duplicate. Confirm the save. The user is logged out. 7. Relogin as the example patron and find the parent record. Click on Components and see there are now two child records. Koha did save the record, but inappropriately logged out the user. I would not expect the cataloger to need the edit_items permission because the user is not editing an item, but duplicating a bibliographic record. 8. Repeat the steps but grant the example patron the edit_items permission. See that the user is able to add a new child record and is not logged out. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 30411] New: Add separate shelving location column to Holds Queue
by bugzilla-daemon＠bugs.koha-community.org 28 Oct '25

28 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30411 Bug ID: 30411 Summary: Add separate shelving location column to Holds Queue Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: sbrown(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com It would be useful, especially with Bug 29015, for shelving location to be its own column in the Holds Queue. This would allow for more flexibility in how libraries view and sort their queues, especially if it's configurable in Table settings. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 36

[Bug 15461] Add shelving location to holdings table as a separate column
by bugzilla-daemon＠bugs.koha-community.org 28 Oct '25

28 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15461 Owen Leonard <oleonard(a)myacpl.org> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=41126 -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 10190] Overdue notice triggers based on item type
by bugzilla-daemon＠bugs.koha-community.org 28 Oct '25

28 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10190 Michaela Sieber <michaela.sieber(a)kit.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs Signoff |Failed QA --- Comment #193 from Michaela Sieber <michaela.sieber(a)kit.edu> --- We tested several hours and I will provide more feedback this week but here are the most relevant Bugs we found: 1.) Migration scenario have some overdue rule, then apply the patch and do updatabase and yarn buid Error 404 in staff interface Please see Pedros comment 192 In your testplan in comment 183 you write in Part 11: Data Integrity & Persistence 5. Check the database circulation_rules table: - Verify the overdue_X_has_rules rule kind is present Is this the missing piece for the migrated data ? 2.) Adding a trigger for a combination that exists in circ rules it is not possible to configure an overdue trigger with a combination that already exists as a circulation rule. Example to reproduce in ktd with test data: - Go to circ rules (/cgi-bin/koha/admin/smart-rules.pl) - Set a rule for All Libraries / All patron categories / Itemtype Books - Check via SQL: select * from circulation_rules - Go to overdue rules (/cgi-bin/koha/admin/circulation_triggers ) - Set a rule for All Libraries / All patron categories / All Itemtype - Now try to edit the delay for the applied rule with combination All Libraries / All patron categories / Itemtype Books --> Message in blue box "Your changes could not be saved as this circulation trigger was updated elsewhere. Please see the updated trigger below." It is not possible to save / submit - Now edit the delay for the applied rule with combination All Libraries / Patron category Homebound / Itemtype Books --> You can save without problems, if this combination does not exist in the database table circulation_rules 3.) Permissions Error if you are not an admin The Overlay rules are part of the tools and also the permission is part of the tools section. That means that it was enough to give users the edit_notice_status_triggers permission, it was not neccessary to give any administration permission (parameters) . Now you moved the overdue triggers to administration. If you now log in as a person with edit_notice_status_triggers permission you can see the tools module and click on the menu for overdue triggers but then you get the error message "Something went wrong: Error: Authorization failure. Missing required permission(s)." 4.) Edit an existing trigger does not pull delay from database Edit an existing trigger and check that the delay value is 0 , it is not pulled from the database. This is confusing and dangerous because you see the delay value just a few centimeters above in the table. If you save the form, the value in the database is overwritten with 0. To reproduce: follow testplan in comment 183 Part 4.3 -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 34623] Update jQuery-validate plugin to 1.20.0
by bugzilla-daemon＠bugs.koha-community.org 28 Oct '25

28 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34623 cking(a)uttyler.edu changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |cking(a)uttyler.edu -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 35647] New: Coce images won't load on the staff results page
by bugzilla-daemon＠bugs.koha-community.org 28 Oct '25

28 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35647 Bug ID: 35647 Summary: Coce images won't load on the staff results page 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: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com To recreate: 1. Turn on all CoceProviders and IntranetCoce. 2. Set CoceHost to 'https://coce.bywatersolutions.com' 3. Do a search and notice that no Coce images load on the results page. 4. In intranet-tmpl/js/coce.js add a debug line inside the `$("[id^=coce-thumbnail]").each(function() {` loop. 5. Nothing happens! This div is being prematurely removed via intranet-tmpl/prog/js/pages/results.js I don't think it is safe to remove the Coce div's without first knowing that KOHA.coce is finished. In results.js: 102 $(window).load(function() { 103 verify_cover_images(); 104 }); Just using a window load is not good enough. We either need to not remove the div ( hiding it is safer ) or we need to use a callback, promise, or async/await. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16