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

[Bug 42909] New: Suspend class missing from suspended holds on request.pl
by bugzilla-daemon＠bugs.koha-community.org 06 Oct '26

06 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42909 Bug ID: 42909 Summary: Suspend class missing from suspended holds on request.pl Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: emily.lamancusa(a)montgomerycountymd.gov QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, lisette(a)bywatersolutions.com, tomascohen(a)gmail.com Depends on: 23269 Target Milestone: --- When viewing the holds list for a particular biblio record, the tr (table row) elements previously had a "suspend" class, allowing CSS styling of suspended holds. As of 25.11.05, that class is missing. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23269 [Bug 23269] Long hold queues are slowing the service -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 21

[Bug 41151] New: Vue Additional Fields UX Improvements
by bugzilla-daemon＠bugs.koha-community.org 06 Oct '26

06 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41151 Bug ID: 41151 Summary: Vue Additional Fields UX Improvements Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com The additional fields input UI's could do with some improvements as noted in bug 38262. To summarise: 1) Spacing between 'Clear' and 'New' buttons on input fields needs work 2) When viewing repeatable, searchable fields in display tables we use a comma separated list instead of field per line. 3) When viewing fields in details display the alignment of the addiional field labels and container is inconsistent I'd go further on point one and ask why we need 'Clear' as a distinct element as it's inconsistent with the 'normal' field entry input boxes. I think I'd prefer to try and make additional fields as consistent as possible with normal input fields, perhaps embedding a 'x' clear check within the far right of input fields to give that 'Clear' functionality accross both additional field and normal field inputs. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 103

[Bug 42032] New: Add diff support to AUTHORITIES action logs
by bugzilla-daemon＠bugs.koha-community.org 06 Oct '26

06 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42032 Bug ID: 42032 Summary: Add diff support to AUTHORITIES action logs Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Transaction logs Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org Blocks: 37940 The action logging in C4/AuthoritiesMarc.pm for authority record changes currently passes unstructured text (or the literal string 'authority') to logaction(). No structured diff is generated in the action_logs.diff column. Affected calls in C4/AuthoritiesMarc.pm: - AUTHORITIES/ADD (~line 688): logaction( "AUTHORITIES", "ADD", $authid, "authority" ) - AUTHORITIES/DELETE (~line 755): logaction( "AUTHORITIES", "DELETE", $authid, "authority" ) - AUTHORITIES/MODIFY (~line 792): logaction( "AUTHORITIES", "MODIFY", $authid, "authority BEFORE=>" . $oldrecord->as_formatted ) This bug covers updating these calls to pass structured data. A Koha::Authority object (or its unblessed hashref) should be passed as $infos and $original so that the structured diff mechanism can generate a proper before/after comparison. The MODIFY case already captures the old record; this should be passed as $original in the new structured format. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37940 [Bug 37940] [OMNIBUS] All modification logged via action logs should include original to create JSON diff -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 62

[Bug 42188] New: Fix display regressions in action logs for biblio changes
by bugzilla-daemon＠bugs.koha-community.org 06 Oct '26

06 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42188 Bug ID: 42188 Summary: Fix display regressions in action logs for biblio changes Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org Depends on: 40135 When we introduced the diff for biblio changes into the action logs, we migrated from MARC::Record->as_formatted to Biblio->unblessed plus some special handling for the attached marc record. Whilst this was following the pattern from elsewhere it actually has some unintended consequences for display (character encoding, field ordering etc) and it is no longer possible to automatically reconstruct the record because a hash does not guarantee fields order and the dollar sign we introduce may occur within the field content. Let's reconsider this and perhaps use marc_in_json. We will need to also take into account non-ascii characters and encoding. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40135 [Bug 40135] Record diff in action logs when modifying a bibliographic record -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 56

[Bug 35145] New: Add ability to order patron attributes
by bugzilla-daemon＠bugs.koha-community.org 06 Oct '26

06 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35145 Bug ID: 35145 Summary: Add ability to order patron attributes Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org Right now, patron attributes are presented in code order. It would be nice to have a way to choose the order in which they are presented. I put this in OPAC because I noticed this in the self-registration form. But I guess it would be true for the staff interface too. My actual use case was for birth details of a baby. I had the birthdate, the number of weeks and the number of days of pregnancy, the weight of the baby, the surname of the baby, etc. I had specifically added them in the order I wanted because I thought the creation order would be the display order. But they were displayed in code order, and the order made no sense (file number, number of days of pregnancy, birth date of the baby, surname of the baby, weight at birth, number of weeks of pregnancy). I thought something like a "Display order" field like the ones we have in serial patterns and numbering and in the additional contents would be useful. To recreate: 1. Create several patron attributes with various codes 1.1. Go to Administration > Patron attribute types > New patron attribute type 1.2. Fill out the form - Code: enter any code, for example WEIGHT - Description: enter any description - Display in OPAC: check - Editable in OPAC: check 1.3. Click Save 1.4. Repeat to add a second code with a code alphabetically "before" the previous one, for example SURNAME 1.5. Optionnally, add more to really view the order 2. Enable self-registration 2.1. Go to Administration > System preferences 2.2. Search for selfreg 2.3. Set PatronSelfRegistration to Allow 2.4. Set a category in PatronSelfRegistrationDefaultCategory 2.5. Click Save all OPAC preferences 3. View self-registration form 3.1. Go to the OPAC 3.2. Click on Don't have an account? Register here. 3.3. Go to the bottom of the form --> Note that the patron attribute fields are presented in alphabetical order of the code. -- You are receiving this mail because: You are watching all bug changes.

1 172

[Bug 42190] New: Add datatables to reports
by bugzilla-daemon＠bugs.koha-community.org 06 Oct '26

06 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42190 Bug ID: 42190 Summary: Add datatables to reports Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: lisette(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: lisette(a)bywatersolutions.com Markus made a really neat datatables plugin: https://github.com/mpathy/KohaDatatables4Reports/tree/main I think it would be a great feature for core Koha. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 73

[Bug 43075] New: Add Content Cafe (formerly Baker & Taylor) back into Koha
by bugzilla-daemon＠bugs.koha-community.org 06 Oct '26

06 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43075 Bug ID: 43075 Summary: Add Content Cafe (formerly Baker & Taylor) back into Koha Initiative type: --- Sponsorship --- status: Product: Koha Version: 26.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: jzairo(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Target Milestone: --- Following the shutdown of Baker and Taylor, Bug 41479 Remove Baker & Taylor integration, was created and pushed to the 26.05 release. LibraryOne has taken over ContentCafe and is available for libraries. This bug is to add the code back into koha system preferences. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9

[Bug 41319] New: Link content of 'Contributing companies and institutions' to bug sponsors
by bugzilla-daemon＠bugs.koha-community.org 06 Oct '26

06 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41319 Bug ID: 41319 Summary: Link content of 'Contributing companies and institutions' to bug sponsors Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: About Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org Right now the 'Contributing companies and institutions' list on the about page is a simple hard-coded list in the template. We should maintain this in a similar way to the rest of the team detail in a yaml file of contributors and have a script to pull these out of the 'Sponsored-by' trailers in git which are much better maintained now and even give a clear link back to what the sponsoring organisation contributed. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 21

[Bug 42169] New: Unify patron category change popups
by bugzilla-daemon＠bugs.koha-community.org 06 Oct '26

06 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42169 Bug ID: 42169 Summary: Unify patron category change popups Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons 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(a)bywatersolutions.com On members/memberentry.pl if you change a patron category you will get 2 pop ups, one after the other. The first is a JS alert asking if you want to update patron messaging settings. The 2nd is a modal popup aking if you want to update the patron date expiry. This isn't very good UX. It would be nice if these could be unified into a single popup or at the very least, be similar types of popups. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 36

[Bug 39863] New: It would be nice to have a command line tool that does bibliographic deduplication with different set parameters
by bugzilla-daemon＠bugs.koha-community.org 06 Oct '26

06 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39863 Bug ID: 39863 Summary: It would be nice to have a command line tool that does bibliographic deduplication with different set parameters Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: enica(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Since we have dedup_authorities.pl, it would be nice to have something for bibliographic records as well. Ideally, the script would dedupe bib records with specified deduplication parameters. For instance, if multiple records have the same isbn, title, author, itemtype, dedupe and merge to a record that is either more complete or has been recently catalogued. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1