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

[Bug 40855] New: Standard backend uses plain SQL
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40855 Bug ID: 40855 Summary: Standard backend uses plain SQL Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: lisette(a)bywatersolutions.com, pedro.amorim(a)openfifth.co.uk, tomascohen(a)gmail.com The edititem() method in the Standard ILL backend uses raw SQL queries with manual delete-all-and-recreate patterns instead of leveraging Koha's ORM. This approach creates several problems: it bypasses ORM validation and relationships, uses inefficient delete-all-then-insert operations that update unchanged attributes, includes complex conditional SQL based on column existence checks [1], and makes the code harder to maintain and debug. The method contains over 40 lines of raw SQL that could be replaced with a single call to add_or_update_attributes() (from bug 40850), which would be more efficient (only updating changed values), safer (using ORM validation), more maintainable (no raw SQL). [1] For backwards compatibility with older Koha versions? Inherited from the time it was an external backend. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 41009] New: When editing an ILL request, the user is returned to the list
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41009 Bug ID: 41009 Summary: When editing an ILL request, the user is returned to the list Change sponsored?: --- 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 It should return to the request. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 18

[Bug 31215] New: Add ability to select multiple items to remove from course_items
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31215 Bug ID: 31215 Summary: Add ability to select multiple items to remove from course_items Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Course reserves Assignee: koha-bugs(a)lists.koha-community.org Reporter: hebah(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Currently the only way to remove items from course reserves is to remove all reserves or select items individually to remove. For libraries that use course reserves with large courses, the ability to select multiple items at a time to remove would be helpful. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 42762] New: Click on quantity will decrease quantity even the number of items increased on neworderempty
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42762 Bug ID: 42762 Summary: Click on quantity will decrease quantity even the number of items increased on neworderempty Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: bibliothek(a)th-wildau.de QA Contact: testopia(a)bugs.koha-community.org - on a new ktd go to /cgi-bin/koha/acqui/neworderempty.pl?booksellerid=1&basketno=1 (Acquisitions -> Search Vendors -> My Vendor -> Baskets -> My Basket -> Add to basket -> From a new (empty) record - enter a title and koha item type - add item - select a fund and save - in the orders table click modify on the just created order - add another item - then click in the quantity field, which is read only. Click outside. - notice the alert 'You can't add a new item, please create a new order line' - quantity is reset to 1 even though the items list on top shows 2 items -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 24414] New: Can't add/delete funds with only budget_add_del permission
by bugzilla-daemon＠bugs.koha-community.org 02 Jun '26

02 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24414 Bug ID: 24414 Summary: Can't add/delete funds with only budget_add_del permission Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org This is very minor, but I was trying out all the permissions to better document them in the manual and I found something weird. There are several permissions granting access to funds. - budget_add_del described as 'Add and delete funds (but can't modify funds)' - budget_manage described as 'Manage funds' - budget_manage_all described as 'Manage all funds' - budget_modify described as 'Modify funds (can't create lines but can modify existing ones)' If I only have budget_add_del, I can't create or delete funds. I have to have budget_manage to access the funds administration page. Which is ok, I can simply add a note in the manual that budget_add_del requires budget_manage. If I have budget_add_del and budget_manage, I have access to the funds administration page, but not the 'New fund' button nor the 'Actions' button to delete an existing fund. So in reality, I can't add nor delete funds... If I have budget_manage and budget_modify (but not budget_add_del), I can't add new funds I can't edit existing ones, but I can delete them. To test : 1) Create a patron and give them the catalogue permission and the budget_add_del permission 2) Log in with this patron (I use a private window to be able to go back and change their permissions later without logging out again) 3) Go to the Acquisitions page 4) Notice you can see the budget, but you can't click on the fund code and you don't have the 'Funds' link in the left menu 5) Go back to edit the user's permissions and grant them budget_manage; save 6) Go back to the Acquisition page with the limited patron (refresh if needed) 7) Notice that you can now click on the fund code and you have a 'Funds' link on the left side of the screen 8) Click on the fund code 9) Click on 'New' and choose 'Add fund for xx'; add the new fund 10) Notice there is no 'Actions' button from which you can delete this fund 11) Go back to edit the user's permissions and remove the budget_add_del permission and add the budget_modify; save 12) Go back to the Acquisition page with the limited patron (refresh if needed) 13) Click on the 'Actions' button and choose 'Edit'; the page refreshes, but nothing happens 14) Click on the 'Actions' button and choose 'Delete' and confirm; the fund is deleted I have trouble imagining a situation where we would want staff to be able to add and delete funds but not modify them, so that's why I said I think this is minor. I think in most cases, the staff member will have at least all three (budget_add_del, budget_manage and budget_modify). But I still wanted to record the weirdness somewhere. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 32919] New: Patron category transitions should be managed in the interface, not on the command line
by bugzilla-daemon＠bugs.koha-community.org 02 Jun '26

02 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32919 Bug ID: 32919 Summary: Patron category transitions should be managed in the interface, not on the command line Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: wizzyrea(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When a library wants to configure transitions between patron categories using the update_patrons_category.pl cron, all of the parameters for this must be entered on the command line. We should put the power to configure this in the hands of the library, and allow configuring these transitions in the Patron Category editor within the interface. We'll still need the cron of course, to do the actual shifting, but how cool would it be to have one job that checks the categories preferences and does the work without needing several job definitions. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 42759] New: Hidding fields or subfields with "Flagged" checkbox or in hidding all views in MARC framework do not work well.
by bugzilla-daemon＠bugs.koha-community.org 02 Jun '26

02 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42759 Bug ID: 42759 Summary: Hidding fields or subfields with "Flagged" checkbox or in hidding all views in MARC framework do not work well. 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: koha(a)collecto.ca QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl In the configuration of a MARC framework, the "Flagged" function, intended to prevent a subfield from appearing in the OPAC, in the editor, or in the intranet, does not seem to behave as expected. Fields or subfields who's "Flagged" has been checked should not appear anywhere, even if the fields are not empty. However, we see these fields appearing in the editor, in the MARC view of the OPAC, and on the intranet (even if all subfields are flagged). Also, if I leave all the boxes unchecked so that they do not appear anywhere (the same behavior as "Flagged", according to the Koha manual), I still see the information in the editor and on intranet if a subfield is filled (if it is empty, I no longer see the field). This is therefore in contradiction with the Koha manual. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 42753] New: item-api-client.js: items.get() should accept headers parameter instead of hardcoding x-koha-embed
by bugzilla-daemon＠bugs.koha-community.org 02 Jun '26

02 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42753 Bug ID: 42753 Summary: item-api-client.js: items.get() should accept headers parameter instead of hardcoding x-koha-embed Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com ItemAPIClient.items.get(id) hardcodes x-koha-embed: '+strings' in the request headers. This should be passed through from the caller (like getAll already does) so different consumers can request different embeds. Current: get: id => this.httpClient.get({ endpoint: 'items/' + id, headers: { 'x-koha-embed': '+strings' }, }), Should be: get: (id, params = {}) => this.httpClient.get({ endpoint: 'items/' + id, ...params, }), Callers that need +strings would pass it explicitly: APIClient.item.items.get(id, { headers: { 'x-koha-embed': '+strings' } }) This follows the same pass-through pattern used for bundled_items.add(). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 42758] New: Resending notices needs more information
by bugzilla-daemon＠bugs.koha-community.org 02 Jun '26

02 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42758 Bug ID: 42758 Summary: Resending notices needs more information Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: martin.renvoize(a)openfifth.co.uk When you resend a notice, the only change to the information on the notice is the updated column. This does not show any reason for the resend or how many times it is resent, or if anything changed from the last time (like the address). It would be helpful if resends were nested and showed the address it was sent to for each attempt. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 34134] New: When viewing an authority details page the search bar is defaulted to the current records authority type
by bugzilla-daemon＠bugs.koha-community.org 02 Jun '26

02 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34134 Bug ID: 34134 Summary: When viewing an authority details page the search bar is defaulted to the current records authority type Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org This was true in previous versions, but is less visible now. To recreate: 1 - Search authorities for "John" 2 - Click on "Uniform title: Jack Johnson" 3 - View the details page, ooooh 4 - Decide to search for John again 5 - This time you get one result? 6 - Click the settings in the search box 7 - Note you have been defaulted to 'Uniform title' authority type -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4