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

[Bug 40663] New: Package GD::Barcode::QRcode@2.01
by bugzilla-daemon＠bugs.koha-community.org 02 Jul '26

02 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40663 Bug ID: 40663 Summary: Package GD::Barcode::QRcode@2.01 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: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org On Ubuntu 24.04, the shipped version of the library is v2.00. Debian 12 has v0.01. The feature it self works fine on either, but v2.00 introduced a warning that is making our test suite to fail [1]. On version v2.01 the author fixed the warning [2] To reproduce: 1. Start an Ubuntu 24.04 KTD: $ KOHA_IMAGE=main-noble ktd --name noble up -d 2. Run: $ ktd --name noble --shell k$ pmvers GD::Barcode::QRcode => 2.00 3. Run: k$ prove t/db_dependent/Koha/Auth/TwoFactorAuth.t => FAIL: Tests fail! 4. Run: k$ sudo cpanm -i GD::Barcode::QRcode@2.01 5. Repeat 3 => SUCCESS: Tests pass! 6. Exit the 24.04 KTD and stop it: k$ exit $ ktd --name noble down 7. Start a Debian 12 KTD: $ KOHA_IMAGE=main-bookworm ktd --name bookworm up -d 8. Run: $ ktd --name bookworm --shell k$ pmvers GD::Barcode::QRcode => 0.01 9. Run: k$ prove t/db_dependent/Koha/Auth/TwoFactorAuth.t => SUCCESS: Tests pass! 10. Run: k$ sudo cpanm -i GD::Barcode::QRcode@2.01 11. Repeat 9 => SUCCESS: Tests still pass! [1] https://jenkins.koha-community.org/job/Koha_Main_U24/lastCompletedBuild/con… [2] https://github.com/mbeijen/GD-Barcode/commit/85e7911e65bf1c4746d9ce2e743580… -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 32

[Bug 42252] Stored XSS when deleting a list or removing a list share
by bugzilla-daemon＠bugs.koha-community.org 02 Jul '26

02 Jul '26

1 0

[Bug 42254] DOM XSS via tag search
by bugzilla-daemon＠bugs.koha-community.org 02 Jul '26

02 Jul '26

1 0

[Bug 42253] Stored XSS in advanced editor in Macro name
by bugzilla-daemon＠bugs.koha-community.org 02 Jul '26

02 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42253 David Cook <dcook(a)prosentient.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Pushed to main |Needs documenting -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 42253] Stored XSS in advanced editor in Macro name
by bugzilla-daemon＠bugs.koha-community.org 02 Jul '26

02 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42253 David Cook <dcook(a)prosentient.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- Version(s)|26.05.00,25.11.04,25.05.10, |26.05.00,25.11.04,25.05.10, released in|24.11.15 |24.11.15,22.11.37 -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 42253] Stored XSS in advanced editor in Macro name
by bugzilla-daemon＠bugs.koha-community.org 02 Jul '26

02 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42253 David Cook <dcook(a)prosentient.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- Version(s)|26.05.00,25.11.04,25.05.10, |26.05.00,25.11.04,25.05.10, released in|24.11.15,22.11.37 |24.11.15 -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 42253] Stored XSS in advanced editor in Macro name
by bugzilla-daemon＠bugs.koha-community.org 02 Jul '26

02 Jul '26

1 0

[Bug 42978] New: Renewal window
by bugzilla-daemon＠bugs.koha-community.org 02 Jul '26

02 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42978 Bug ID: 42978 Summary: Renewal window Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com Target Milestone: --- Should renewals have a window of time (both manual and auto) for renewals, in order to prevent checkout abuse. Consider, you have ManualRenewalPeriodBase set to "the old duedate of the checkout". You check it out, and the patron or staff at some point before it is due hits renewal (either on accident or on purpose). For this scenario, lets say it is done right after checkout. This could effectively work around limits to not renew if the item goes on hold. If the library allows a couple of renewals, this prevents bringing the item back sooner if others are waiting for the item. I haven't seen such a window, but allowing a window of x number of days before and after the due date to renew would make sense, to limit people gaming the checkout period. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 42917] New: Error when changing existing hold from item/record level with only place_holds permission
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '26

01 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42917 Bug ID: 42917 Summary: Error when changing existing hold from item/record level with only place_holds permission Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests 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, lisette(a)bywatersolutions.com, tomascohen(a)gmail.com Target Milestone: --- To recreate: 1/ Create or find a user with place_hold permission but not the top level permission 2/ Place a hold 3/ From reserve/request.pl?biblionumber=X try to change the hold from record to item, or vice versa. 4/ See popup: There was an error:error Forbidden -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 42960] New: Database update 25.12.00.059 attempts Elasticsearch mapping update when SearchEngine is Zebra
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '26

01 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42960 Bug ID: 42960 Summary: Database update 25.12.00.059 attempts Elasticsearch mapping update when SearchEngine is Zebra Initiative type: --- Sponsorship --- status: Product: Koha Version: 26.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Installation and upgrade (command-line installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: mark(a)hofstetter.at QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com Target Milestone: --- When upgrading a Koha instance to 26.05, db revision 25.12.00.059 (Bug 40658 - Ensure local-number is sortable) unconditionally instantiates Koha::SearchEngine::Elasticsearch::Indexer and calls update_mappings(). This happens even when the instance has SearchEngine = Zebra. On a Zebra-only instance without Elasticsearch configured, koha-upgrade-schema fails and blocks the entire schema upgrade: Upgrade to 25.12.00.059: Bug 40658 - Ensure local-number is sortable ERROR: Exception 'Koha::Exception' thrown 'Unable to update mappings for index "koha_lise_biblios". Reason was: "". Index needs to be recreated and reindexed' Reproduced in koha-testing-docker with KOHA_IMAGE=26.05, SearchEngine=Zebra, by resetting Version to 25.1200058 and setting local-number sort=0. Expected behavior: - The DB revision should still set search_marc_to_field.sort = 1. - Elasticsearch mappings should only be updated if SearchEngine is Elasticsearch. - Zebra-only instances should not require Elasticsearch to complete koha-upgrade-schema. Proposed fix: Guard the Elasticsearch mapping update with: if ( C4::Context->preference('SearchEngine') eq 'Elasticsearch' ) { ... } and report that the ES mapping update was skipped otherwise. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3