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

[Bug 41337] New: koha-create --request-db and --populate-db creates log files owned by root (intranet-error.log, opac-error.log)
by bugzilla-daemon＠bugs.koha-community.org 17 Jul '26

17 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41337 Bug ID: 41337 Summary: koha-create --request-db and --populate-db creates log files owned by root (intranet-error.log, opac-error.log) Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: Linux Status: NEW Severity: major Priority: P5 - low Component: Installation and upgrade (command-line installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: saiful(a)semanticconsulting.com QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com When creating a new Koha instance using the two-step workflow (--request-db and --populate-db), some log files under /var/log/koha/<instance>/ end up with incorrect permissions. Specifically, intranet-error.log and opac-error.log are created as root:root instead of <inst>-koha:<inst>-koha. This causes Apache/Plack to fail to start cleanly until the ownership is corrected manually. Steps to Reproduce: 1. Run: koha-create --request-db test 2. Create the DB/user on the remote or local DB host as instructed. 3. Then run: koha-create --populate-db test 4. Check ownership of generated logs: ls -l /var/log/koha/test Actual Result: Two files are owned by root:root: -rw-r--r-- 1 root root 0 intranet-error.log -rw-r--r-- 1 root root 0 opac-error.log All other logs have correct ownership (test-koha:test-koha). Koha will not start smoothly until these two files are manually chowned. Expected Result: All log files under /var/log/koha/<instance>/ should be owned by <instance>-koha:<instance>-koha, identical to a normal koha-create run without the request/populate split. Notes: This only happens when using the two-step creation (--request-db + --populate-db). A normal one-step koha-create with --create-db assigns the correct ownership. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 21

[Bug 37397] New: "Barcodes" in preservation module untranslatable
by bugzilla-daemon＠bugs.koha-community.org 17 Jul '26

17 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37397 Bug ID: 37397 Summary: "Barcodes" in preservation module untranslatable Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: I18N/L10N 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: f.demians(a)tamil.fr, jonathan.druart(a)gmail.com When adding items to the waiting list in the preservation module, the "Barcodes" hint in the text box is not translatable. To get there: 1. Install another language e.g. ./misc/translator/translate update fr-CA ./misc/translator/translate install fr-CA Enable the language in the language syspref 2. Enable PreservationModule syspref 3. Add a not for loan status in the PreservationNotForLoanWaitingListIn syspref 4. Change the language of the interface 5. Go to Preservation > Waiting list 6. Click Add to waiting list --> The "Barcodes" hint inside the text box is not translated 7. Optionally, search the .po files for the string git grep "Barcodes" fr-CA* --> Nothing for preservation; everything else is translated -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 41047] New: Current library and home library sort by code instead of description
by bugzilla-daemon＠bugs.koha-community.org 17 Jul '26

17 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41047 Bug ID: 41047 Summary: Current library and home library sort by code instead of description Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl To recreate: 1. Find or create a record with items from multiple home/holding libraries. 2. Attempt to sort by either Current library and Home library 3. Notice that they sort by code instead of description. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20

[Bug 41058] New: Using Show Checkouts button when LoadCheckoutsTableDelay is set causes collision/error. loadIssuesTableDelayTimeoutId not assigned
by bugzilla-daemon＠bugs.koha-community.org 17 Jul '26

17 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41058 Bug ID: 41058 Summary: Using Show Checkouts button when LoadCheckoutsTableDelay is set causes collision/error. loadIssuesTableDelayTimeoutId not assigned Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: mike.grgurev(a)mainlib.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com Manually selecting the "Show Checkouts" button does not cancel the setTimeout associated with LoadCheckoutsTableDelay (Checkouts table will show automatically in blah seconds..) In /intranet-tmpl/prog/js/checkouts.js, loadIssuesTableDelayTimeoutId is declared and targeted by clearTimeout() but never applied to the setTimeout() that triggers LoadIssuesTable(). Lines 712 & 735 should be revised from "setTimeout(function () {" to "loadIssuesTableDelayTimeoutId = setTimeout(function () {" -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 29

[Bug 41335] New: Toggling the hold options does not always work in opac-reserve
by bugzilla-daemon＠bugs.koha-community.org 17 Jul '26

17 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41335 Bug ID: 41335 Summary: Toggling the hold options does not always work in opac-reserve Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, lisette(a)bywatersolutions.com, tomascohen(a)gmail.com Some combinations of OPACMandatoryHoldDates together with forced item level holds make the options collapsed while they should be expanded. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 22

[Bug 41073] New: Import users expiry date default does not apply
by bugzilla-daemon＠bugs.koha-community.org 17 Jul '26

17 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41073 Bug ID: 41073 Summary: Import users expiry date default does not apply Initiative type: --- Sponsorship --- status: Product: Koha Version: 24.11 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: bernard.scaife(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com You can no longer set an expiry date into the past. Test file: userid,cardnumber,branchcode,categorycode,surname "12345","65432","LONDON","STANDARD","Smith" 1. User should exist and have expiry date in future (say 2099-12-31) 2. Save above as file 3. Tools > Import users 4. Choose file saved in 2 5. Field to use for record matching: cardnumber 6. In default values set expiration date to a date in past (say 2025-10-19) using date picker 7. Select overwrite the existing one with this 8. Leave renew existing patrons as "use the expiration date in the file if present" 9. Run 10. Observe user expiry date is still 2099-12-31 NB/ Tested in 23.11.10 where the date was correctly set to the default value chosen -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 24

[Bug 28884] New: ElasticSearch: Question mark in title search returns no results
by bugzilla-daemon＠bugs.koha-community.org 17 Jul '26

17 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28884 Bug ID: 28884 Summary: ElasticSearch: Question mark in title search returns no results Change sponsored?: --- Product: Koha Version: 20.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: jyorio(a)equinoxinitiative.org When searching for a title with a question mark, Who's Afraid of Virginia Woolf? for example, Koha returns no results with ElasticSearch. Removing the question mark or escaping it retrieves results, as does enclosing the entire title with the question mark in quotes. Since ? is a wildcard for ElasticSearch, this may be expected behavior (I'm not sure that it is or isn't), but explaining to patrons that they need to change their search behavior can be a big ask for libraries. Not sure what the best option is. Perhaps a system preference to automatically escape ? and not treat it as a wildcard for those libraries who would prefer that? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 60

[Bug 35237] New: Duplicate ids in markup of patron card layout edit form
by bugzilla-daemon＠bugs.koha-community.org 17 Jul '26

17 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35237 Bug ID: 35237 Summary: Duplicate ids in markup of patron card layout edit form Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Keywords: Academy, accessibility Severity: minor Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: testopia(a)bugs.koha-community.org Tools -> Patron card creator -> Edit layout: A few pairs of radio buttons have duplicate labels: <li> <label for="page_side">Page side: </label> <input type="radio" name="page_side" id="page_side" value="F">Front <input type="radio" name="page_side" id="page_side" value="B" checked="checked">Back </li> It would be better for the "Page side" label to have no "for" attribute and for "Front" and "Back" to be labels. -- You are receiving this mail because: You are watching all bug changes.

1 25

[Bug 40568] New: Various corrections to recalls templates
by bugzilla-daemon＠bugs.koha-community.org 17 Jul '26

17 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40568 Bug ID: 40568 Summary: Various corrections to recalls templates Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 40560, 40566 I've got a few random corrections to make to a couple of recalls templates. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40560 [Bug 40560] Incorrect breadcrumb on recall history https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40566 [Bug 40566] "Home library" empty on "Recalls history" -- You are receiving this mail because: You are watching all bug changes.

1 20

[Bug 41043] New: Use op 'add_form' and 'edit_form' instead of 'add' and 'edit'
by bugzilla-daemon＠bugs.koha-community.org 17 Jul '26

17 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41043 Bug ID: 41043 Summary: Use op 'add_form' and 'edit_form' instead of 'add' and 'edit' Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Since CSRF protection, 'op' arg for creating/editing an object uses add_form and edit_form. This is missing only in admin/oai_servers.pl and admin/z3950servers.pl -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 20