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

[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 34811] New: Old image viewer not accessible in OPAC
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34811 Bug ID: 34811 Summary: Old image viewer not accessible in OPAC Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Also found following the test plan from bug 34724: There is no link to the image viewer present on the OPAC detail page. If any of the local covers is clicked from the images tab, the preview/thumbnails of the other images are missing on the right side. Test plan: 0. Apply the patch (including dependent patches) 1. Go to http://localhost:8081/cgi-bin/koha/admin/preferences.pl?tab=&op=search&sear… 2. Change both *LocalCoverImages sysprefs to "Show" 3. Go to http://localhost:8081/cgi-bin/koha/admin/preferences.pl?tab=&op=search&sear… 4. Change "AllowMultipleCovers" to "Allow" 5. Go to http://localhost:8081/cgi-bin/koha/catalogue/detail.pl?biblionumber=29 6. Click "Images (0)" tab 7. Download or make two JPEG images 8. Upload the images 9. Go to http://localhost:8080/cgi-bin/koha/opac-imageviewer.pl?biblionumber=29 10. See one large image in the centre and two smaller thumbnails on the right side The link from the iamges tab for a single cover is: http://localhost:8080/cgi-bin/koha/opac-imageviewer.pl?biblionumber=29&imag… The preview is missing. -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 35637] New: Batch patrons modification - add "Preferred language for notices"
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35637 Bug ID: 35637 Summary: Batch patrons modification - add "Preferred language for notices" 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: pierre.genty(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com In Batch patrons modification, field "Preferred language for notices" is missing. It should be useful to add it. -- 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 34929] New: Allow automatic removal of users from ERM agreements and licenses
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34929 Bug ID: 34929 Summary: Allow automatic removal of users from ERM agreements and licenses Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ERM Assignee: jonathan.druart+koha(a)gmail.com Reporter: holly(a)bywatersolutions.com CC: jonathan.druart+koha(a)gmail.com, jonathan.field(a)ptfs-europe.com, martin.renvoize(a)ptfs-europe.com, matt.blenkinsop(a)ptfs-europe.com, pedro.amorim(a)ptfs-europe.com Currently users must be manually removed from agreements and licenses in the ERM module. It would be more efficient to have an option to remove a user from any ERM agreements or licenses they are connected to when the ERM permission is disabled on that user's account. -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 34696] New: Leaving on screen keyboard enabled breaks advanced editor
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34696 Bug ID: 34696 Summary: Leaving on screen keyboard enabled breaks advanced 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 To recreate 1. Edit catalog record in Advanced Editor 2. Turn on the on screen keyboard with ctrl-shift-k 3. Select keyboard layout for French-azerty-1 4. Hit enter at the end of a tag line to add a new tag. 5. Enter tag number at start of new line. 6. Hit tab twice to add indicator spaces. Entering tab twice for the indicator spaces fails as the indicator underscores does not appear. Also the tab space amount is incorrect as it adds too many spaces and bypasses the normal start point for the first delimiter. A delimiter can be added, but it is in the incorrect place and shows as red. Having the onscreen keyboard enabled while editing allows for quick insertion of diacritics. It would be expected that enabling the keyboard would not interfere with the ability to edit the record. The current work around is to enable the keyboard and layout to select the correct diacritic to insert and then disable it to continue editing the record. This can be problematic when multiple diacritics need to be inserted. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 36488] New: Flatpickr creates invalid date entries
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36488 Bug ID: 36488 Summary: Flatpickr creates invalid date entries Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org I believe that in some conditions flatpickr creates invalid date entries that can be saved. To test: * Switch DateFormat to DD.MM.YYY * Go to the OPAC self registration form * Enter a date of 00.00.000 * It will show as: 30.12.00-1 in the input and can be saved We have seen something similar on bug 36466. -- You are receiving this mail because: You are watching all bug changes.

1 35

[Bug 38374] New: process_message_queue can send duplicate mails if Password Recovery used while queue is running
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38374 Bug ID: 38374 Summary: process_message_queue can send duplicate mails if Password Recovery used while queue is running Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: philip.orr(a)lmscloud.de QA Contact: testopia(a)bugs.koha-community.org If the process_message_queue process has been started and is not yet finished running and a patron uses the Password Recovery function in the OPAC, mails that were due to be sent by process_message_queue can be accidentally duplicated and sent out multiple times. In our case the message queue was running around 05:00 AM ish and was not yet done. While it was running, a patron somehow used the OPAC Password Recovery function 10 times in a single second, maybe it was possible that their internet was down, they clicked on the password recovery link 10 times, then their internet went back up and the HTTP requests were sent. Anyway process_message_queue then sent 10 duplicates of all mails that were still not yet sent. Unfortunately I'm not really sure how to reproduce the issue. You could try: - have message queue running and not yet finished with mails to your own email address - use the password recovery function in the OPAC - see if duplicate mails land in your inbox -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2