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

[Bug 41686] New: Strange unescaping of html-entities in itemcallnumber
by bugzilla-daemon＠bugs.koha-community.org 03 Feb '26

03 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41686 Bug ID: 41686 Summary: Strange unescaping of html-entities in itemcallnumber Initiative type: --- Sponsorship --- status: Product: Koha Version: 25.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: andreas.jonsson(a)kreablo.se QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Go to a bibliographic record and edit an item. In itemcallnumber type: a & Save. The result is, as expected, that the itemcallnumber will be literally 'a &' Edit the item again and change to a & b Save. Now the itemcallnumber will be 'a & b' as if the string has been subject to an extra unescaping of html-entities. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 31268] New: Clearly indicate reason for failed item creation when receiving expired subscription
by bugzilla-daemon＠bugs.koha-community.org 03 Feb '26

03 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31268 Bug ID: 31268 Summary: Clearly indicate reason for failed item creation when receiving expired subscription Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrewfh(a)dubcolib.org QA Contact: testopia(a)bugs.koha-community.org Bug 29188 points out that while the manual says one cannot receive issues in an expired subscription, Koha is currently allowing one to do so. However, Koha *is* refusing to create an item when receiving an issue on an expired subscription. To recreate: 1 - create a subscription set to *not* create items, subscription end date in the past 2 - save subscription, confirm it shows as expired, confirm you can receive an issue anyway 3 - create a subscription set *to* create items, subscription end date in the past 4- save subscription, confirm it shows as expired, confirm you can get to the receiving page but setting the dropdown for the expected issue to "Arrived" does not cause an item edit box to appear 5- create a subscription set *to* create items, subscription end date in the future, number of issues set to 1 6- save subscription, receive 1 issue, confirm it works as intended 7- confirm subscription now shows a confusing "Subscription will expire on [subscription end date]" message even though the date isn't the problem 8- Attempt to receive another issue, confirm that now the item edit box won't pop up, as in step 4 In steps 4 and 8, the item edit box will appear if one attempts to receive a supplemental issue, but the item will refuse to save, giving an erroneous "missing required field" message. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 41494] New: Rename "Koha administration" to "Administration" for consistency
by bugzilla-daemon＠bugs.koha-community.org 03 Feb '26

03 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41494 Bug ID: 41494 Summary: Rename "Koha administration" to "Administration" for consistency Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: david(a)davidnind.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com We use "Koha administration" in only two places in the staff interface: - The label for the module on the staff interface home page - The page heading on the administration module home page Everywhere else, we normally just use "Administration", for example: - All the breadcrumbs for the areas in the administration page are just Administration > ... - The same for browser page titles in this area ... > Administration > Koha - More > Administration Change to just "Administration" would improve consistency, and is what we normally call it. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14

[Bug 41329] New: yarn install generates 2 warnings regarding datatables-.net-vue3
by bugzilla-daemon＠bugs.koha-community.org 03 Feb '26

03 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41329 Bug ID: 41329 Summary: yarn install generates 2 warnings regarding datatables-.net-vue3 Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 38426 warning " > datatables.net-vue3(a)2.1.3" has unmet peer dependency "datatables.net(a)^1.13.1". warning " > datatables.net-vue3(a)2.1.3" has unmet peer dependency "jquery(a)^3.6.0". How is that bad? Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38426 [Bug 38426] Node.js v18 EOL around 25.05 release time -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 41102] New: Error 500 on the "About" page when biblioserver Zebra configuration is missing
by bugzilla-daemon＠bugs.koha-community.org 03 Feb '26

03 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41102 Bug ID: 41102 Summary: Error 500 on the "About" page when biblioserver Zebra configuration is missing 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: hammat.wele(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org When either the <listen id="biblioserver"> entry or the <server id="biblioserver" listenref="biblioserver"> section is not present in koha-conf.xml, the Intranet > About page triggers a 500 Internal Server Error. To test: 1. Edit koha-conf.xml and Comment out:  2. Restart Apache: sudo systemctl restart apache2 3. Go to Intranet -> About ==> Internal Server Error (500) 4. Now restore the <listen> line and instead comment out the entire <server id="biblioserver" listenref="biblioserver">...</server> block. 5. Repeat step 2, 3 ==> Internal Server Error (500) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 38876] New: Typo in UpdateNotForLoanStatusOnCheckout description
by bugzilla-daemon＠bugs.koha-community.org 03 Feb '26

03 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38876 Bug ID: 38876 Summary: Typo in UpdateNotForLoanStatusOnCheckout description Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: aude.charillon(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com In the description of the UpdateNotForLoanStatusOnCheckout system preference, the sentence: "When an item is checked out, if the not for loan value on the left matches the items not for loan value it will be updated to the right-hand value" should be corrected to "When an item is checked out, if its not for loan value matches the value on the left, then the item's not for loan value will be updated to the value on the right". -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 27

[Bug 38739] New: Templates not ending with include intranet-bottom.inc in staff interface
by bugzilla-daemon＠bugs.koha-community.org 03 Feb '26

03 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38739 Bug ID: 38739 Summary: Templates not ending with include intranet-bottom.inc in staff interface Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Some templates in staff interface do not end with include intranet-bottom.inc. > tail -n1 koha-tmpl/intranet-tmpl/prog/en/modules/*/*.tt | grep -B2 '</html>' ==> koha-tmpl/intranet-tmpl/prog/en/modules/acqui/showorder.tt <== </html> -- ==> koha-tmpl/intranet-tmpl/prog/en/modules/basket/basket.tt <== </html> ==> koha-tmpl/intranet-tmpl/prog/en/modules/basket/downloadcart.tt <== </html> ==> koha-tmpl/intranet-tmpl/prog/en/modules/basket/sendbasketform.tt <== </html> ==> koha-tmpl/intranet-tmpl/prog/en/modules/batch/print-notices.tt <== </html> -- ==> koha-tmpl/intranet-tmpl/prog/en/modules/catalogue/showelastic.tt <== </html> ==> koha-tmpl/intranet-tmpl/prog/en/modules/catalogue/showmarc.tt <== </html> -- ==> koha-tmpl/intranet-tmpl/prog/en/modules/reports/convert_report.tt <== </html> -- ==> koha-tmpl/intranet-tmpl/prog/en/modules/tools/preview_letter.tt <== </html> -- ==> koha-tmpl/intranet-tmpl/prog/en/modules/virtualshelves/downloadshelf.tt <== </html> ==> koha-tmpl/intranet-tmpl/prog/en/modules/virtualshelves/sendshelfform.tt <== </html> So for example it does not call hook "intranet_js". Should all templates end with this include ? -- You are receiving this mail because: You are watching all bug changes.

1 62

[Bug 12141] On Display Module
by bugzilla-daemon＠bugs.koha-community.org 03 Feb '26

03 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12141 Gretchen Maxeiner <maxeinergl(a)gcc.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |maxeinergl(a)gcc.edu -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14964] Email notices will be queued for patrons with no email address and generate warnings
by bugzilla-daemon＠bugs.koha-community.org 03 Feb '26

03 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14964 Lari Taskula <lari.taskula(a)hypernova.fi> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lari.taskula(a)hypernova.fi --- Comment #8 from Lari Taskula <lari.taskula(a)hypernova.fi> --- (In reply to Katrin Fischer from comment #4) > Wondering... should we queue a message of the type 'print' if there is no > e-mail address? I think this might be what we do for overdues > ... but probably should be configurable - for some notices you might not > want to have a printed one Definitely should be configurable. The volume of print messages could become massive if it was a mandatory fallback, and most of the patrons, though having no email address, would have enabled email notifications. It would happen when a library, that has enabled some default messaging preferences from the patron category, doesn't systemically collect patron email addresses. If we absolutely must fallback to some type of messaging, I'd rather display them in OPAC notifications from Bug 36006. I also remember developing code for messaging preferences where one could not check email messaging preferences before providing the email address, but it seems that functionality has not yet made it into Koha. (probably Bug 18595 patch (follow-up) Disable transports if missing contact information) -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15522] New interface for revamped circulation rules
by bugzilla-daemon＠bugs.koha-community.org 03 Feb '26

03 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15522 Michaela Sieber <michaela.sieber(a)kit.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=41439 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0