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

[Bug 33073] New: sip_cli_emulator doesn't work and documentation is in error
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33073 Bug ID: 33073 Summary: sip_cli_emulator doesn't work and documentation is in error Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: bob-ewart(a)bobsown.com QA Contact: testopia(a)bugs.koha-community.org The documentation on SIP2 server setup gives an example of running the sip_cli_emulator: ./misc/sip_cli_emulator.pl -a 127.0.0.1 -p 6001 -su term1 -sp term1 \ -l CPL --patron 23529001000463 -m checkout --item 39999000001259 it responds with No such file or directory running: /usr/share/koha/bin/sip_cli_emulator.pl -a 127.0.0.1 -p 6001 -l SLA -su <loginID> -sp <login password> --patron <myID> --password <my password> -m patron_information it responds with Can't locate C4/SIP/Sip/Constants.pm running: perl -I /usr/share/koha/lib /usr/share/koha/bin//sip_cli_emulator.pl -a localhost ... it responds with: Attempting socket connection to localhost:6001...connected! Use of uninitialized value $hold_mode in string eq at /usr/share/koha/bin//sip_cli_emulator.pl line 122. SEND: 9300CNSLAAdmin_sip2|COst0newall1972|CPSLA| READ: 940 Login Failed! That user/password is in SIPconfiguration.xml. It's category is Staff and has permissions: Check out and check in items Staff access Place and modify holds for patrons Manage patrons fines and fees Manage the electronic resources module I can log in with that ID and password -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 33232] New: report on item types
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33232 Bug ID: 33232 Summary: report on item types Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: library(a)princeofpeaceabbey.org QA Contact: testopia(a)bugs.koha-community.org The report on item types seems to be stuck. The numbers do not change even though I have added more items. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 34222] New: Add ability to use non-sequential barcodes when adding multiple copies of an item
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34222 Bug ID: 34222 Summary: Add ability to use non-sequential barcodes when adding multiple copies of an item Change sponsored?: --- Product: Koha Version: 22.11 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 Currently when adding multiple copies of an item the system assigns sequential barcodes based on the barcode entered on the first item. It would be nice to be able to scan the barcodes that should be assigned to the copies, especially if the library does not use sequential barcodes. This could be accomplished by clicking add multiple copies of this item and having a box appear where barcodes could be scanned. The barcodes can then be assigned to the number of copies. It is not necessary to assign specific barcodes to specific items because the items are identical copies. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 34168] New: Make it possible to configure display sequence of additional fields
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34168 Bug ID: 34168 Summary: Make it possible to configure display sequence of additional fields Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, michaela.sieber(a)kit.edu At the moment it's not possible to make the additional fields appear in a logical order. It would be great if it was possible to optionally configure the sequence in which the fields appear in edit forms and in tables. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 34262] New: Merging duplicate patrons in succession is adding previously merged duplicate
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34262 Bug ID: 34262 Summary: Merging duplicate patrons in succession is adding previously merged duplicate Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: esther.melander(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Merging duplicate patrons in succession is adding previously merged duplicates into the merge options. To Recreate: 1. Self-register Patron A multiple times through the OPAC. 2. Self-register Patron B multiple times through the OPAC. 3. Search for Patron A and merge some of the duplicates. 4. Search for Patron B and select some of the duplicates. On the next screen selected Patron B duplicates will be shown as well as the previously merged account of Patron A. 5. Select a Patron B account as the surviving record and proceed to merge. Patron B accounts are merged to the surviving record as well as Patron A's account, causing Patron A to no longer exist. The current work around is to log out of the staff account and log back in. This seems to clear the session data and allow the proper selections to appear, minus the previously merged account. However, this is not practical when needing to merge a lot of accounts. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 10

[Bug 34175] New: Unable to delete certain tags in basic editor
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34175 Bug ID: 34175 Summary: Unable to delete certain tags in basic editor Change sponsored?: --- Product: Koha Version: 22.11 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 When editing a biblio in the basic editor, it is not possible to delete certain tags. It is possible to delete subject tags such as 600, 650, etc. But it is not possible to delete a blank 007 despite the icon for delete tag being present. If leaving a blank tag has no impact, then the delete tag icon should be removed. Otherwise, the delete tag ability should be enabled. It is confusing for it to be present if the tag should not be deleted. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 34330] New: Saving while leaving 942 $c blank (required field) in fast cataloging causes random redirection
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34330 Bug ID: 34330 Summary: Saving while leaving 942 $c blank (required field) in fast cataloging causes random redirection Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: normal 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. Ensure fast add framework has at least two required fields. 245 $a Title and 942 $c item type 2. Go to cataloging module and fast cataloging 3. Choose a title already existing in the system in order to trigger a duplicate warning. 4. Enter a title only and leave 942 $c blank 5. Get a Duplicate record suspected warning with the option to Yes, edit exiting items or No, save as new record. Select No, save as new record. >From here random things happen depending on the permissions of the patron. If the patron has full cataloging permissions it will open a new Add MARC record blank form, skipping the warning about a blank required field. If the patron only has fast cataloging permission it will log the patron out of the system. What should happen in both cases is a block with a warning that the 942 $c is blank. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 34361] New: Search by date for invoices to close gives Error
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34361 Bug ID: 34361 Summary: Search by date for invoices to close gives Error Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: dch(a)interleaf.ie QA Contact: testopia(a)bugs.koha-community.org Since 22.11, in invoices.pl, if you search by date and then select one or more invoices to Close, you get Error 500. Template process failed: undef error - The given date (01/10/2019) does not match the date format (iso) at /usr/share/koha/lib/Koha/DateUtils.pm line 205. The invoice(s) are actually closed. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[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 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