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

[Bug 39176] New: Update additional_field_values.record_id to varchar(255)
by bugzilla-daemon＠bugs.koha-community.org 30 Jan '26

30 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39176 Bug ID: 39176 Summary: Update additional_field_values.record_id to varchar(255) Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org In bug 38663 we had to switch from int(11) to varchar(11) so we could properly store branchcode, the primary key for the branches table. In bug 38457 I'm now faced with the same issue of needing to update the field from varchar(11) to varchar(80) to allow for the code field in the account_debit_types table which is a varchar(80) primary key. Looking to the future and how we're starting to add more and more uses of additional fields I think we should pick the largest current primary key field and match that. SELECT t.TABLE_NAME AS table_name, k.COLUMN_NAME AS primary_key_field, CASE WHEN k.CHARACTER_MAXIMUM_LENGTH IS NOT NULL THEN CONCAT(k.DATA_TYPE, '(', k.CHARACTER_MAXIMUM_LENGTH, ')') WHEN k.NUMERIC_PRECISION IS NOT NULL THEN CONCAT(k.DATA_TYPE, '(', k.NUMERIC_PRECISION, ')') ELSE k.DATA_TYPE END AS primary_key_type FROM INFORMATION_SCHEMA.TABLES t JOIN INFORMATION_SCHEMA.COLUMNS k ON t.TABLE_NAME = k.TABLE_NAME AND t.TABLE_SCHEMA = k.TABLE_SCHEMA JOIN INFORMATION_SCHEMA.KEY_COLUMN_USAGE ku ON t.TABLE_NAME = ku.TABLE_NAME AND t.TABLE_SCHEMA = ku.TABLE_SCHEMA AND k.COLUMN_NAME = ku.COLUMN_NAME JOIN INFORMATION_SCHEMA.TABLE_CONSTRAINTS tc ON ku.TABLE_NAME = tc.TABLE_NAME AND ku.TABLE_SCHEMA = tc.TABLE_SCHEMA AND ku.CONSTRAINT_NAME = tc.CONSTRAINT_NAME WHERE t.TABLE_SCHEMA = DATABASE() AND tc.CONSTRAINT_TYPE = 'PRIMARY KEY' ORDER BY t.TABLE_NAME; Using the above query, I believe that shows the largest is a varchar(255). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 24288] New: Add wording to authorized value interface to indicate valid code length
by bugzilla-daemon＠bugs.koha-community.org 30 Jan '26

30 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24288 Bug ID: 24288 Summary: Add wording to authorized value interface to indicate valid code length Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Several standard authorized values feed into fields that require a single character code (LOST, NOTFORLOAN, DAMAGED, RESTRICTED, WITHDRAWN). It'd be good to have some wording in the authorized value interface that would indicate this. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 29

[Bug 23861] New: Add authorised value categories description option
by bugzilla-daemon＠bugs.koha-community.org 30 Jan '26

30 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23861 Bug ID: 23861 Summary: Add authorised value categories description option Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration 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 I really like the way the authorised values page looks now. I think it's much more user friendly with the descriptions and the categories all laid out and not in a drop-down. Right now, the descriptions for each category are "hardcoded" in the template. Would it be feasible to move those in the DB? That way, when we add new categories, we would be able to add our own description. For example, if I add a category for RDA media type, I would be able to add a description saying it's meant to be used with 337$a. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 27512] New: Block creation of invalid authorised values for LOST, NOTFORLOAN, DAMAGED, RESTRICTED, and WITHDRAWN
by bugzilla-daemon＠bugs.koha-community.org 30 Jan '26

30 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27512 Bug ID: 27512 Summary: Block creation of invalid authorised values for LOST, NOTFORLOAN, DAMAGED, RESTRICTED, and WITHDRAWN Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Several authorised value categories have inherent limits on what values can be used. Bug 24288 adds text to the screen to tell you about these limits, but doesn't enforce them. It'd be good to just stop a user from saving a value that won't work. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 36067] New: Inconsistencies in --commit, --confirm for command line scrips
by bugzilla-daemon＠bugs.koha-community.org 30 Jan '26

30 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36067 Bug ID: 36067 Summary: Inconsistencies in --commit, --confirm for command line scrips Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Our scripts have a mix of --commit and --confirm to 'actually do the job'. I think we should try to be consistent here.. with the most backward compatible option being to make them synonyms in each script. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 37669] New: Add 'auto_account_expired' to AUTO_RENEWALS_DGST
by bugzilla-daemon＠bugs.koha-community.org 30 Jan '26

30 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37669 Bug ID: 37669 Summary: Add 'auto_account_expired' to AUTO_RENEWALS_DGST Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: r.delahunty(a)arts.ac.uk QA Contact: testopia(a)bugs.koha-community.org We added the account expired error to our digest and find it useful. [% ELSIF checkout.auto_renew_error == 'auto_account_expired' %] [% checkout.item.biblio.title %] (barcode: [% checkout.item.barcode %]) could not be renewed as your account has expired. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 29557] New: auto-renew notices should handle failed renewal due to patron expiration
by bugzilla-daemon＠bugs.koha-community.org 30 Jan '26

30 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29557 Bug ID: 29557 Summary: auto-renew notices should handle failed renewal due to patron expiration Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The default auto-renew and auto-renew-digest notices should include logic to tell patrons when their renewals have failed due to upcoming patron expiration. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 21

[Bug 35655] New: Make it possible to switch off RabbitMQ without any warns in logs/about page
by bugzilla-daemon＠bugs.koha-community.org 30 Jan '26

30 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35655 Bug ID: 35655 Summary: Make it possible to switch off RabbitMQ without any warns in logs/about page Change sponsored?: --- Product: Koha Version: master 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org A recent survey on IRC revealed that a lot of people are still running Koha without RabbitMQ. It's not a small dependency and for smaller libraries it might not be needed ever. Also we still see issues with jobs not being processed correctly that has people turning it off. We should not create any warns or logs, but have a proper switch to turn RabbitMQ off without Koha complaining until we can fully rely on RabbitMQ at least. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 51

[Bug 40826] New: nbofuser not incremented when using a mana report
by bugzilla-daemon＠bugs.koha-community.org 29 Jan '26

29 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40826 Bug ID: 40826 Summary: nbofuser not incremented when using a mana report Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Mana-kb Assignee: koha-bugs(a)lists.koha-community.org Reporter: elias.lorgnier(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: alex.arnaud(a)biblibre.com When importing a report from mana, the nbofuser dosen't go up as it should. By looking at the code, I think that feature is not implemented, even though the function Koha::SharedContent::increment_entity_value, wich works for subscriptions is implemented. It is simply never used with reports. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 12

[Bug 21781] New: message_transport_type should allow fallbacks
by bugzilla-daemon＠bugs.koha-community.org 29 Jan '26

29 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21781 Bug ID: 21781 Summary: message_transport_type should allow fallbacks Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Bug 21241 adds the ability for a fallback from email to sms when a patron email address isn't found on the suggestions notices. This shouldn't be limited to suggestions, but be a more comprehensive piece of work to capture other hard coded message transports. opac/svc/checkout_notes opac/opac-issue-note.pl opac/opac-memberentry.pl opac/opac-shareshelf.pl circ/pendingreserves.pl circ/article-request-slip.pl C4/Reserves.pm C4/Acquisition.pm misc/cronjobs/automatic_renewals.pl misc/cronjobs/membership_expiry.pl misc/cronjobs/stockrotation.pl Koha/ArticleRequests.pm Koha/Patron/Password/Recovery.pm Koha/Account.pm All of the above have a message_transport_type hard coded to some degree.. some may be better served left as is.. but many would benefit from a fallback. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 48