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

[Bug 42699] New: Editing an already received serial with a duplicate barcode leads to Error 500
by bugzilla-daemon＠bugs.koha-community.org 10 Jun '26

10 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42699 Bug ID: 42699 Summary: Editing an already received serial with a duplicate barcode leads to Error 500 Initiative type: --- Sponsorship --- status: Product: Koha Version: 25.05 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: lauri.hanninen(a)lahti.fi QA Contact: testopia(a)bugs.koha-community.org When you edit an already received serial from Serial collection page using Edit serials and edit items buttons, and try to save a barcode that already exists on another item, saving leads to Error 500. Apparently there's no validation on the serial module's edit page which causes that problem. Steps to Reproduce: -Go to serials module -Search for a serial that is not expired to edit and click on the title -Go to Serial collection from the menu -Use the checkboxes to mark an already received (eg. usually older, arrived, not expected) serial and click Edit serials -Click on Edit item -Replace the barcode with a unique barcode that is already in use and hit save -> Error 500 Actual Results: Saving changes returns Error 500. Expected Results: Validation returns a duplicate barcode value/already in use error and doesn't try to save before a valid and unique barcode is given. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[Bug 15248] Make it possible to configure duplicate check on bibliographic records
by bugzilla-daemon＠bugs.koha-community.org 10 Jun '26

10 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15248 Thibaud Guillot (thibaud_g) <thibaud.guillot(a)biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #198490|0 |1 is obsolete| | --- Comment #48 from Thibaud Guillot (thibaud_g) <thibaud.guillot(a)biblibre.com> --- Created attachment 200177 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=200177&action=e… Bug 15248: (QA follow-up) Clear merge errors and tidy -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15248] Make it possible to configure duplicate check on bibliographic records
by bugzilla-daemon＠bugs.koha-community.org 10 Jun '26

10 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15248 Thibaud Guillot (thibaud_g) <thibaud.guillot(a)biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #198489|0 |1 is obsolete| | --- Comment #47 from Thibaud Guillot (thibaud_g) <thibaud.guillot(a)biblibre.com> --- Created attachment 200176 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=200176&action=e… Bug 15248: (QA follow-up) Add POD Signed-off-by: Andrew Fuerste Henry <andrew(a)bywatersolutions.com> -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15248] Make it possible to configure duplicate check on bibliographic records
by bugzilla-daemon＠bugs.koha-community.org 10 Jun '26

10 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15248 Thibaud Guillot (thibaud_g) <thibaud.guillot(a)biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #198488|0 |1 is obsolete| | --- Comment #46 from Thibaud Guillot (thibaud_g) <thibaud.guillot(a)biblibre.com> --- Created attachment 200175 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=200175&action=e… Bug 15248: Set forbid_duplicate_creation as boolean in schema Signed-off-by: Andrew Fuerste Henry <andrew(a)bywatersolutions.com> -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15248] Make it possible to configure duplicate check on bibliographic records
by bugzilla-daemon＠bugs.koha-community.org 10 Jun '26

10 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15248 Thibaud Guillot (thibaud_g) <thibaud.guillot(a)biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #198487|0 |1 is obsolete| | --- Comment #45 from Thibaud Guillot (thibaud_g) <thibaud.guillot(a)biblibre.com> --- Created attachment 200174 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=200174&action=e… Bug 15248: [DO NOT PUSH] Update DBIC schema Signed-off-by: Andrew Fuerste Henry <andrew(a)bywatersolutions.com> -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15248] Make it possible to configure duplicate check on bibliographic records
by bugzilla-daemon＠bugs.koha-community.org 10 Jun '26

10 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15248 Thibaud Guillot (thibaud_g) <thibaud.guillot(a)biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #198486|0 |1 is obsolete| | --- Comment #44 from Thibaud Guillot (thibaud_g) <thibaud.guillot(a)biblibre.com> --- Created attachment 200173 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=200173&action=e… Bug 15248: Use record matching rules to find duplicate while cataloging This patch allows to configure how Koha searches for duplicates when cataloging manually by using a record matching rule. For each framework we can now set a record matching rule to use when searching for duplicates. This allow to use different matching rules while in acquisition for instance (ACQ framework). If a matching rule is selected, we also have the ability to forbid the creation of duplicate: if a duplicate is found and this option is enabled, the usual option to create a duplicate will be hidden. If no matching rule is selected, then the default matching mechanism is used. Test plan: 1. Create a record matching rule matching on ISBN Threshold: 100 Record type: biblio Match point: Search index: "isbn" Score: 100 Tag: "020" (or "010" for UNIMARC) Subfields: "a" Offset: 0 Length: 0 Normalization rule: Remove spaces No match checks 2. Edit the default MARC framework and select the new matching rule and enable "Forbid duplicate creation" 3. Create a biblio with an ISBN 4. Make sure your new biblio is indexed in Zebra or ES 5. Try to create a biblio with the same ISBN. You should see a warning about the duplicate with no option to create the duplicate biblio 6. In the acquisitions module, in a basket add a new order from an external source (requires a configured Z39.50/SRU server) 7. Choose a record with an ISBN 8. Once the order is created, try to create a new order from an external source and choose the same record. You should see a warning about the duplicate. 9. Edit the record matching rule and disable "Forbid duplicate creation" 10. Redo step 5. Now there should be an option to create the duplicate record. 11. Redo step 8. Now there should be an option to create the duplicate record. 12. Run the following test scripts: - t/db_dependent/Search.t - t/db_dependent/Matcher.t Sponsored-by: SCD Lyon2 Signed-off-by: Andrew Fuerste Henry <andrew(a)bywatersolutions.com> Signed-off-by: Jeanne Maurielle <jeanne.mauriello(a)mainlib.org> Signed-off-by: Andrew Fuerste Henry <andrew(a)bywatersolutions.com> -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15248] Make it possible to configure duplicate check on bibliographic records
by bugzilla-daemon＠bugs.koha-community.org 10 Jun '26

10 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15248 Thibaud Guillot (thibaud_g) <thibaud.guillot(a)biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Patch doesn't apply |Needs Signoff -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 42374] New: DB Upgrade from the UI is broken
by bugzilla-daemon＠bugs.koha-community.org 10 Jun '26

10 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42374 Bug ID: 42374 Summary: DB Upgrade from the UI is broken Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: blocker Priority: P5 - low Component: Installation and upgrade (command-line installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com >From bug 17438 comment 17 Thats how i reproduce it: - git checkout v25.11.03-2 - reset_all - git checkout main - restart_all - open koha and run web installer -> error occurs If you run updatedatabase in shell the error is not thrown ISBN_RANGE_MESSAGE is set to [] but that file does not exist! Trying to use the default locations -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 40

[Bug 41460] New: On Mysql on upgrade from 25.05 to 25.11 I got the error TEXT column 'value' can't have a default value
by bugzilla-daemon＠bugs.koha-community.org 10 Jun '26

10 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41460 Bug ID: 41460 Summary: On Mysql on upgrade from 25.05 to 25.11 I got the error TEXT column 'value' can't have a default value Initiative type: --- Sponsorship --- status: Product: Koha Version: 25.11 Hardware: All OS: All Status: NEW Severity: blocker Priority: P5 - low Component: Database Assignee: koha-bugs(a)lists.koha-community.org Reporter: michael.hafen(a)washk12.org QA Contact: testopia(a)bugs.koha-community.org Mysql does not allow blob or text type columns to have a default. The systempreferences.value column is the only occurrence of this I found in the kohastructure.sql file. It seems Mysql will ignore the default null as long as the column allows null, so that's not an issue. Bug 40405 sets systempreferences.value to NOT NULL, but tries to also add a DEFAULT '', which causes Mysql to throw the above error. Proposed solution is to remove the DEFAULT '' part of the clause from the db_rev file. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 27

[Bug 28957] Many plugins require the full plugins permission set to run
by bugzilla-daemon＠bugs.koha-community.org 10 Jun '26

10 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28957 --- Comment #12 from David Cook <dcook(a)prosentient.com.au> --- (In reply to Luis Bataller from comment #11) > We've actually been carrying a local patch for this at Xercode for over a > year now, and it's basically David's comment #8 (option 2): an optional > plugin hook that lets the plugin say which permissions a given method needs. Thanks for adding that, Luis. I think Bywater are doing work on refactoring Koha's permission system, so it could be useful for you to join the discussion on that as well: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20813 -- You are receiving this mail because: You are watching all bug changes.

1 0