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

[Bug 22458] New: PatronSelfRegistrationEmailMustBeUnique disallows self modification requests if multiple accounts share an email address
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '26

27 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22458 Bug ID: 22458 Summary: PatronSelfRegistrationEmailMustBeUnique disallows self modification requests if multiple accounts share an email address Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: jrobb(a)sekls.org QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- PatronSelfRegistrationEmailMustBeUnique causes unexpected behavior on the patron self modification screen ("your personal details") in the OPAC. When enabled, the system preference blocks existing accounts from submitting account modification requests if the primary email associated with the account is also associated with another account in the database. This means if a parent account and a child account both use the same email address, neither can submit account modification requests via the OPAC. This system preference should only affect new self registered accounts. To reproduce this behavior: 1. Set PatronSelfRegistrationEmailMustBeUnique to 'Consider' 2. Create two different accounts with the same primary email address 3. Log into the OPAC with either account 4. Visit "your personal details" 5. Make a change unrelated to email address and submit 6. The submission is blocked with a message about duplicate email addresses -- You are receiving this mail because: You are watching all bug changes.

1 16

[Bug 39169] New: Acq column configurations are lacking (parent ticket 11578)
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '26

27 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39169 Bug ID: 39169 Summary: Acq column configurations are lacking (parent ticket 11578) Change sponsored?: --- Product: Koha Version: 24.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: tgoatley(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 178369 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=178369&action=e… Budget screen shot with columns at issue HI Koha Dev's! The Acquisitions home page is displaying two columns that should be hidden by default (see screenshot) The first column is 'Active' and the second is 'Budget period description.' I don't think they were displayed previous to 24.11. Plus the the info is distracting, clutters up the display and is not useful. I checked the column settings to see if I could hide them but the 'Is hidden by default' setting is greyed out but not checked. The 'Cannot be toggled' setting is both greyed out and checked. (Submitted on behalf of Barbara at Bedford Public Library in Bedford Texas) Cheers! Todd -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 18

[Bug 39079] New: Matchpoints with multiple fields require all fields to match under Elasticsearch
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '26

27 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39079 Bug ID: 39079 Summary: Matchpoints with multiple fields require all fields to match under Elasticsearch Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org In zebra when matching an incoming file to existing records, we use 'OR' to combine the fields In elasticsearch we are combining multiple fields with 'AND' as a 'must' search This means an incoming record with two control numbers will not match an existing record with only one The generated queries are like: 2025-02-10T14:59:07 zebrasrv(46) [request] Search authorities OK 0 1 1+0 RPN @attrset Bib-1 @or @attr 1=Local-Number @attr 4=109 @attr 7=1 0 @or @or @attr 6=3 @attr 5=100 @attr 4=1 @attr 1=other-control-number (DE-588)4179998-7 @attr 6=3 @attr 5=100 @attr 4=1 @attr 1=other-control-number (DE-627)104628669 @attr 6=3 @attr 5=100 @attr 4=1 @attr 1=other-control-number (DE-576)209995106 versus 'bool' => { 'must' => [ { 'term' => { 'other-control-number.ci_raw' => '(DE-588)4179998-7' } }, { 'term' => { 'other-control-number.ci_raw' => '(DE-627)104628669' } }, { 'term' => { 'other-control-number.ci_raw' => '(DE-576)209995106' } } ] } } This is due to this bit of code: ElasticSearch/QueryBuilder: 469 # Merge the query parts appropriately 470 # 'should' behaves like 'or' 471 # 'must' behaves like 'and' 472 # Zebra behaviour seem to match must so using that here 473 my $elastic_query = {}; 474 $elastic_query->{bool}->{must} = \@query_parts; We need to respect the and_or passed into build_auth_query_compat, but currently: 514 =item and_or 515 516 Totally ignored. It is never used in L<C4::AuthoritiesMarc::SearchAuthorities>. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 39070] New: Elasticsearch Facets are not used/needed when finding record matches
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '26

27 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39070 Bug ID: 39070 Summary: Elasticsearch Facets are not used/needed when finding record matches Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org We have found that in production, when loading large record sets, we can sometimes overload the ES server and cause timeouts. One possible cause here is the cost of generating facets (aggregations) when looking for matching records. We don't use the values here, so shouldn't request them -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 38861] New: error in bookings to collect
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '26

27 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38861 Bug ID: 38861 Summary: error in bookings to collect Change sponsored?: --- Product: Koha Version: 24.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: jzairo(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Created attachment 176372 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=176372&action=e… 200 error When loading the bookings to collect report in the circulation module an error appears. 'Something went wrong when loading the table. 200:ok. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 25

[Bug 38762] New: compare_es_to_db.pl should provide links to the staff interface
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '26

27 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38762 Bug ID: 38762 Summary: compare_es_to_db.pl should provide links to the staff interface Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz The script currently generates a link to the OPAC URLs for the affected records. It should generate links we can copy and paste to access the records for fixing them. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 38294] New: Checkbox/label for search filters incorrectly aligned
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '26

27 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38294 Bug ID: 38294 Summary: Checkbox/label for search filters incorrectly aligned Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org https://snipboard.io/vBcSKs.jpg -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 38939] New: Add reservenote to members/holdshistory.pl
by bugzilla-daemon＠bugs.koha-community.org 26 Feb '26

26 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38939 Bug ID: 38939 Summary: Add reservenote to members/holdshistory.pl Change sponsored?: --- 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 For some libraries it would be handy to show the reserve note on the hold history page for a patron. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 28

[Bug 37439] New: ChildNeedsGuarantor description misleading
by bugzilla-daemon＠bugs.koha-community.org 26 Feb '26

26 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37439 Bug ID: 37439 Summary: ChildNeedsGuarantor description misleading Change sponsored?: --- Product: Koha Version: Main 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 Unless I misunderstood the purpose of the ChildNeedsGuarantor system preference, I think the description is misleading. It currently states A child patron [doesn't need/must have] a guarantor when adding the patron. However, this is not limited to children. It affect patrons whose patron category is set to 'can be guarantee'. I'm not sure what the best formulation would be. Maybe something like When a patron category is set to 'can be guarantee', the guarantor is [mandatory / not mandatory]. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 26

[Bug 31124] New: koha-remove fails to remove long_tasks queue daemon, so koha-create for same <instance> user fails
by bugzilla-daemon＠bugs.koha-community.org 26 Feb '26

26 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31124 Bug ID: 31124 Summary: koha-remove fails to remove long_tasks queue daemon, so koha-create for same <instance> user fails Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Keywords: rel_22_05_candidate Severity: major Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: matted-34813(a)mypacks.net QA Contact: testopia(a)bugs.koha-community.org >From the command line as a koha shell user: 1) koha-remove <instance> fails to remove the backgroundjobs / long_tasks(queue) daemon. (ps -aef | grep long_tasks) So when it tries to "deluser" the <instance>-koha user from /etc/passwd that errors because a process is still running for that user's PID. 2) koha-create <instance> fails for that same instance name from that point onward. 3) koha-worker --help doesn't show any --queue option Cursory investigation shows: --queue support was added in version 22.05 to koha-worker. koha-worker --stop --queue long-tasks <instancename> works to shut down that specified queue. --status and --start are also supported. Suggested Fix: 1) koha-remove needs to have an entry added: koha-worker --stop --queue long_tasks <instancename> added accordingly to get that process to stop so the latter deluser will succeed. 2) koha-worker needs: the --queue option should be added to the --help / POD Also, koha-worker --help should at least show: Usage: koha-worker [--start|--stop|--restart] [--quiet|-q] [--queue <queuename>] instancename1 [instancename2...] and also: --queue <queuename> Specify a queue name One should be able to be able(test plan): test 1) koha-remove kohadev koha-create --create-db kohadev koha-remove kohadev without problems in the ktd or other test environment to be fixed. test 2) Also, koha-worker --help should at least show: Usage: koha-worker [--start|--stop|--restart] [--quiet|-q] [--queue <queuename>] instancename1 [instancename2...] and also: --queue <queuename> Specify a queue name -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 30