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

[Bug 40063] New: Hide auto renewal options if auto renewal is not activated
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '25

03 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40063 Bug ID: 40063 Summary: Hide auto renewal options if auto renewal is not activated Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Some auto renewal options appear all over the staff interface and OPAC even if the library has not activated auto renewals. This is confusing to staff and patrons. Staff interface - In memberentry.pl, there is a yes/no option for "Allow auto-renewal of items" - In memberentry.pl and moremember.pl, there is an option for Auto renewal notice OPAC - In opac-messaging.pl, there is an option for Auto renewal notice I'm not sure if we should have a global on/off switch for autorenewals or if each of these things should have a syspref like AllowSetAutomaticRenewal. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 39931] New: OPAC Sorting by Publication Year (264$c) Does Not Work Correctly
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '25

03 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39931 Bug ID: 39931 Summary: OPAC Sorting by Publication Year (264$c) Does Not Work Correctly Change sponsored?: --- Product: Koha Version: 24.11 Hardware: PC OS: Windows Status: NEW Severity: major Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: shahrum.alias(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 182559 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=182559&action=e… Publication Date: Newest to Oldest / Oldest to Newest not indexing properly In Koha version 24.11, sorting search results by publication year (newest to oldest/oldest to newest) in the OPAC does not work as expected, even though the correct data exists in MARC field `264$c`. The issue appears to be related to how the publication year is indexed or handled during OPAC search result sorting. ### Steps to Reproduce: 1. Enter bibliographic records with valid publication years in MARC field `264$c`. 2. Rebuild Zebra/Elasticsearch index. 3. Perform a general search in the OPAC. 4. Attempt to sort by "Publication Date: Newest to Oldest and oldest to newest". #### Expected Result: - Results should be sorted by publication year descending (e.g., 2024, 2023, 2022). #### Actual Result: - Sorting appears incorrect or inconsistent. - Records do not appear in chronological order by publication year. ### Additional Information: - I have verified that the data is present and sortable via direct SQL query using XPath and regex extraction. - Indexing configuration seems to map `264$c` to `publication_date`, but sorting behavior does not reflect this. - Rebuilding the index did not resolve the issue. - This affects user experience in the public OPAC where accurate sorting by publication date is critical. ### Suggested Fix / Enhancement: 1. Ensure that `264$c` is properly mapped in the Search Engine Configuration for use in `publication_date`. 2. Confirm that the value is normalized and indexed as a numeric field (e.g., only the 4-digit year) for proper sorting. 3. Consider adding documentation or warnings if certain MARC subfields are known to cause issues with sorting/indexing. ```If anyone has experienced this issue before or found a solution, please share your insights!``` -- You are receiving this mail because: You are watching all bug changes.

1 10

[Bug 7915] Print a barcoded membership card from member detail page
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '25

03 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7915 Caroline Cyr La Rose <caroline.cyr-la-rose(a)inlibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |caroline.cyr-la-rose@inlibr | |o.com --- Comment #4 from Caroline Cyr La Rose <caroline.cyr-la-rose(a)inlibro.com> --- Yes please! -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 4858] Ability to Charge for Print Notices
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '25

03 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4858 Martin Renvoize (ashimema) <martin.renvoize(a)openfifth.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|koha-bugs(a)lists.koha-commun |martin.renvoize(a)openfifth.c |ity.org |o.uk CC| |martin.renvoize(a)openfifth.c | |o.uk -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 32506] New: Prevent creation of same fund code within a single budget
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '25

03 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32506 Bug ID: 32506 Summary: Prevent creation of same fund code within a single budget 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: barbara.johnson(a)bedfordtx.gov QA Contact: testopia(a)bugs.koha-community.org When adding funds to a single budget, staff should not be able to create two funds using the same fund code. This happened at our library and wasn’t discovered until we had received titles in the two duplicate fund codes. We then had to combine everything into the one fund code. Keeping the fund codes unique would prevent confusion and staff time it took to fix our mistake. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 40045] New: Shortcuts (i.e. Y or N keys) to not require Alt as well as pressing the specific key
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '25

03 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40045 Bug ID: 40045 Summary: Shortcuts (i.e. Y or N keys) to not require Alt as well as pressing the specific key Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: hdunne-howrie(a)westminster.gov.uk QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com In our old library management system, shortcuts for pop up messages would be a single key, i.e. Y key for Yes to proceed. In Koha, you need to press the Alt key as well as the appropriate key for the operation. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 39184] Server-side template injection leading to remote code execution
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '25

03 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39184 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Passed QA |Pushed to oldoldstable -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 37727] CVE-2024-24337 - Fix CSV formula injection - client side (DataTables)
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '25

03 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37727 --- Comment #26 from David Cook <dcook(a)prosentient.com.au> --- Here's some more info on CSV injection: https://owasp.org/www-community/attacks/CSV_Injection -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 37727] CVE-2024-24337 - Fix CSV formula injection - client side (DataTables)
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '25

03 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37727 --- Comment #25 from David Cook <dcook(a)prosentient.com.au> --- (In reply to Emmi Takkinen from comment #24) > This fix has caused a new problem with exporting, see bug 40015. > > > Now we should upgrade to the last version of DataTables and remove this from > > Koha I guess... > > > > It's fixed there. > > So if we update datatables and drop this, would bug 40015 be resolved with > that? Doesn't look like it. The version in dataTables buttons 3.2.0 is the same thing: https://github.com/DataTables/Buttons/blob/master/js/dataTables.buttons.js#… Looks like more thinking will need to be put into this... -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 39798] New: Add ability to shut off modules completely
by bugzilla-daemon＠bugs.koha-community.org 02 Jun '25

02 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39798 Bug ID: 39798 Summary: Add ability to shut off modules completely Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org I am filing this bug after working with a library that is non-circulating, no patrons. It would be quite nice if we could shut off entire modules with an on/off switch. The idea would be, shut off patrons/members: -I would see no links to patrons/members pages. -The search bar at the top of each page would never show 'Search patrons' -System preferences related to patrons/members would not be shown unless the module was turned on. This is kind of pie in the sky type stuff but it would be nice. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15