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

[Bug 8127] Most-circulated items report doesn't work when limited by library
by bugzilla-daemon＠bugs.koha-community.org 15 Jul '26

15 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8127 --- Comment #12 from Lucas Gass (lukeg) <lucas(a)bywatersolutions.com> --- Created attachment 201967 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=201967&action=e… Bug 8127: Fix filters use in 'Most-circulated items report' Filters are broken for many reasons. Previous patch contains some (little) tidying. There are 3 parts in this patch: 1 - The column name is incorrectly named in the dropdown for "branch", it is added in this patch 2 - There is a definition for 'Day' and 'Month', but not for 'Week', it is also added in this patch 3 - Dbh variables are passed in the string definition AND in the call. I removed them from the string definition since it violates the coding guidelines. Test plan: 1. On an fresh ktd db, run the script provided here (https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8127#c3) to fill the database with checkins/checkouts: Visit http://your_koha:8081/cgi-bin/koha/reports/cat_issues_top.pl 2. Run a baseline test with following params: Checkout date from 01/01/2020 Checkout date to: tomorrow Library: Any library Fill nothing else Notice it is works 3. Test with some limits (Library, Week, and any other), notice you encounter errors on Library and Week, and that any other is empty, without error. 4. Apply patch 5. Rerun 2-3 and notice you now have results. Check with each possible limit, limiting to 5. Test once with 10 as a limit. Signed-off-by: David Nind <david(a)davidnind.com> Signed-off-by: Lucas Gass <lucas(a)bywatersolutions.com> -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8127] Most-circulated items report doesn't work when limited by library
by bugzilla-daemon＠bugs.koha-community.org 15 Jul '26

15 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8127 --- Comment #11 from Lucas Gass (lukeg) <lucas(a)bywatersolutions.com> --- Created attachment 201966 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=201966&action=e… Bug 8127: Remove useless commented warns Signed-off-by: David Nind <david(a)davidnind.com> Signed-off-by: Lucas Gass <lucas(a)bywatersolutions.com> -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8127] Most-circulated items report doesn't work when limited by library
by bugzilla-daemon＠bugs.koha-community.org 15 Jul '26

15 Jul '26

1 0

[Bug 8127] Most-circulated items report doesn't work when limited by library
by bugzilla-daemon＠bugs.koha-community.org 15 Jul '26

15 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8127 Lucas Gass (lukeg) <lucas(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Signed Off |Passed QA -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 25667] New: Add field for items.notforloan_on to record when a notforloan status is applied
by bugzilla-daemon＠bugs.koha-community.org 15 Jul '26

15 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25667 Bug ID: 25667 Summary: Add field for items.notforloan_on to record when a notforloan status is applied Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Database Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org We record lost_on and damaged_on. Can we record notforloan_on, too? It'd be helpful for various reports. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14

[Bug 8127] Most-circulated items report doesn't work when limited by library
by bugzilla-daemon＠bugs.koha-community.org 15 Jul '26

15 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8127 Lucas Gass (lukeg) <lucas(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lucas(a)bywatersolutions.com QA Contact| |lucas(a)bywatersolutions.com -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 43084] New: OPAC ILL request form (Standard backend) should default library to patron's home library
by bugzilla-daemon＠bugs.koha-community.org 15 Jul '26

15 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43084 Bug ID: 43084 Summary: OPAC ILL request form (Standard backend) should default library to patron's home library Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: pedro.amorim(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org CC: lisette(a)bywatersolutions.com, pedro.amorim(a)openfifth.co.uk, tomascohen(a)gmail.com Target Milestone: --- -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 35693] New: Granular Permissions to Everything
by bugzilla-daemon＠bugs.koha-community.org 15 Jul '26

15 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35693 Bug ID: 35693 Summary: Granular Permissions to Everything Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com I don't know exactly how to file this. Koha is growing all the time and new features are always being added, but they are often being added with very little permission granularity. Often the permissions are too broad. For example, the newer pages under additional-contents.pl is under the entire umbrella of one permission for the user, and gives them access to ALL pages, ALL news, and ALL HTML customizations. I am hoping that Koha will start thinking more about roles in the library, and allowing us to give specific people access to specific pages, customizations, etc. This goes even further with who can override things. We don't have a lot of control over who can do what specific things. Maybe there is a bug on this topic already? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 26

[Bug 43080] New: API not functional if Koha::Database->dbh can't connect at app startup time
by bugzilla-daemon＠bugs.koha-community.org 15 Jul '26

15 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43080 Bug ID: 43080 Summary: API not functional if Koha::Database->dbh can't connect at app startup time Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com Target Milestone: --- I noticed earlier today that Koha started up despite API setup errors due to Koha::Database->dbh being unable to connect to the database (during some automated updates). X/plack-api-error.log:[2026/07/15 04:52:43] [ERROR] Warning: Could not load REST API spec bundle: DBIx::Class::Storage::DBI::catch {...} (): DBI Connection failed: DBI connect(<DEETS>,...) failed: Can't connect to MySQL server on 'SERVER:3306' (111) at /usr/share/koha/lib/Koha/Database.pm line 75. at /usr/share/koha/lib/Koha/Database.pm line 125 X/plack-api-error.log:[2026/07/15 04:52:45] [ERROR] Warning: Could not load REST API spec bundle: DBIx::Class::Storage::DBI::catch {...} (): DBI Connection failed: DBI connect(<DEETS>,...) failed: Can't connect to MySQL server on 'SERVER:3306' (111) at /usr/share/koha/lib/Koha/Database.pm line 75. at /usr/share/koha/lib/Koha/Database.pm line 125 Looking at Koha/REST/V1.pm it looks like we catch the errors but we don't do anything if the spec fails to load completely. It might be worthwhile to check the error being thrown in the try/catch and maybe die /rethrow if it is a database connection issue. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 42413] New: Invalid metadata is causing a 500 error when editing
by bugzilla-daemon＠bugs.koha-community.org 15 Jul '26

15 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42413 Bug ID: 42413 Summary: Invalid metadata is causing a 500 error when editing Initiative type: --- Sponsorship --- status: Product: Koha Version: 25.05 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: enica(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl If you get an invalid metadata/character error in the staff client, you used to be able to fix the error by editing and saving the record. Now, it's throwing a 500 error. The only way to fix it is in the backend. It would be nice if Koha could automatically remove invalid metadata/characters. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2