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

[Bug 42833] New: Provider SSO icon size must auto
by bugzilla-daemon＠bugs.koha-community.org 20 Jun '26

20 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42833 Bug ID: 42833 Summary: Provider SSO icon size must auto Initiative type: --- Sponsorship --- status: Product: Koha Version: 26.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: mhby87(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Created attachment 200309 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=200309&action=e… Big icon size not resize like staff login When I active SSO login in KOHA, I used provider Icon URL for login icon. When I click Login into account on OPAC right top, provider icon not resize like staf login or OPAC homepage login. Reffer attachment. Tq -- You are receiving this mail because: You are watching all bug changes.

1 6

[Bug 42489] New: Allow RealTimeHoldsQueue to use --unallocated option
by bugzilla-daemon＠bugs.koha-community.org 19 Jun '26

19 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42489 Bug ID: 42489 Summary: Allow RealTimeHoldsQueue to use --unallocated option Initiative type: --- Sponsorship --- status: 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: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, lisette(a)bywatersolutions.com, tomascohen(a)gmail.com The build_holds_queue from has an "--unallocated" option, which causes it to pick targets for new holds without recalculated holds that already have targets allocated. It would be good for the Real Time queue to also have this option. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 29

[Bug 42777] New: Authority linker cron job removes punctuation
by bugzilla-daemon＠bugs.koha-community.org 19 Jun '26

19 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42777 Bug ID: 42777 Summary: Authority linker cron job removes punctuation Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: mnero(a)oslri.net QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl We have AutoLinkBiblios enabled, so when we save a bib record, the headings are automatically linked. When doing this, if there is a period at the end of a field being linked, the $9 appears after the period. We also have a cron job that runs once a week to run general authority linking on our system. During that process, if there is a period at the end of the field, it removes it when adding the $9. This is causing an issue with the same heading appearing with the period if it was linked upon saving and without the period if it was linked during the cron job. If the period is before a $2 (Fantasy fiction.$2lcgft for example), the cron job will change it to Fantasy fiction$2lcgft, removing the period. While this doesn't seem to affect access or indexing, it creates a problem when searching for specific strings in the fields or sorting exported information from any of those controlled fields. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 39331] New: Guarantor relationships not removed when changing patron category from memberentry.pl
by bugzilla-daemon＠bugs.koha-community.org 19 Jun '26

19 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39331 Bug ID: 39331 Summary: Guarantor relationships not removed when changing patron category from memberentry.pl Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When editing a patron in the staff interface the guarantor relationships are being recreated after they are removed The code calls Patron->store - this is where guarantors are removed when category changes - after this we call add_guarantors using the $input from the form To recreate: 1 - Remove age limits from a Child and Adult category in Administration->Patron categories. Ensure Child category can be guarantor and Adult cannot 2 - The above step is to avoid any age checks and form resubmission which removes the guarantor fields 3 - Find/create a child patron 4 - Add a guarantee from the Adult category to the child 5 - Check the DB: SELECT * FROM borrower_relationships WHERE guarantee_id={borrowernumber of child}; 6 - Note the id colum 7 - Edit the child patron to Adult category 8 - Repeat 5 9 - Note the relationship still exists and the id is incremented 10 - Oof! -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 25

[Bug 39363] New: Warn staff that guarantors are being removed when changing patron category to one that cannot be guarantee
by bugzilla-daemon＠bugs.koha-community.org 19 Jun '26

19 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39363 Bug ID: 39363 Summary: Warn staff that guarantors are being removed when changing patron category to one that cannot be guarantee Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons 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, kyle.m.hall(a)gmail.com >From a discussion on Bug 39331. It would be nice to display some information about the guarantors that will be removed when you switch a patron category to one that cannot be guarantee. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 42803] New: Regression in reports/catalogue_out.pl
by bugzilla-daemon＠bugs.koha-community.org 19 Jun '26

19 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42803 Bug ID: 42803 Summary: Regression in reports/catalogue_out.pl Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: lisette(a)bywatersolutions.com Target Milestone: --- >From Bug 42361: 1) Set strict_sql_modes to 0 in koha-conf.xml and restart plack 2) Go to Reports > Items with no checkouts: <staff_url>/cgi-bin/koha/reports/catalogue_out.pl 3) Leave Library set to "Any library" 4) Pick a specific item type that you know has items (e.g. "BK") 5) Submit, you get 0 results. Without patch you get normal results. If the first filter value is empty (i.e. 'Any library'), the filter key gets skipped which essentially results in items.homebranch LIKE 'BK' (from the test plan above). I think we need this: foreach my $filter (@filters_input) { - if ( Koha::Libraries->find($filter) || Koha::ItemTypes->find($filter) ) { + if ( !$filter || Koha::Libraries->find($filter) || Koha::ItemTypes->find($filter) ) { push( @filters, $filter ); } } -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 22

[Bug 42734] New: autoMemberNumValue syspref has no UI â add it to patrons preferences with a caution note
by bugzilla-daemon＠bugs.koha-community.org 19 Jun '26

19 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42734 Bug ID: 42734 Summary: autoMemberNumValue syspref has no UI â add it to patrons preferences with a caution note Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com Bug 34000 introduced autoMemberNumValue as an internal monotonic counter to prevent cardnumber re-issuance. However there is currently no way for staff to view or correct this value if it becomes inflated â for example, if a book barcode is accidentally scanned when creating a patron and that patron is subsequently deleted or has their cardnumber corrected. This patch adds autoMemberNumValue to the Patrons system preferences page (near autoMemberNum) so that superlibrarians can correct a runaway counter without contacting vendor support. The entry includes a caution note explaining: - that the value is managed automatically and should not normally be changed - that Koha always generates from max(counter, live_db_max), so lowering the counter only has effect once the patron responsible for the inflated number has been deleted or had their cardnumber corrected - the risk of setting it too low (potential cardnumber re-issuance) Test plan: 1. Apply patch 2. Go to Administration > System preferences > Patrons 3. Confirm autoMemberNumValue is visible immediately below the autoMemberNum preference 4. Confirm the caution note is displayed 5. With autoMemberNum enabled, create a patron without specifying a cardnumber and confirm the generated number is consistent with the counter value 6. Adjust autoMemberNumValue to a lower number (after ensuring no active patron holds a cardnumber in that range), create another patron, and confirm the next auto-generated number reflects the corrected counter -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 33

[Bug 42002] New: SIP screen msg regexp can't be empty
by bugzilla-daemon＠bugs.koha-community.org 19 Jun '26

19 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42002 Bug ID: 42002 Summary: SIP screen msg regexp can't be empty Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: marion.durand(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Before the migration of SIP parameters in the interface, it was possible to delete a message by replacing it with an empty string with the following code: ``` <screen_msg_regex find="Greetings from Koha. " replace="" /> ``` It's no longer possible from the interface as the replace field is mandatory (a lot of our library deleted the message "Greetings from Koha. ") -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 41178] New: SIP2 module does not notify that linked accounts are deleted when deleting an institution
by bugzilla-daemon＠bugs.koha-community.org 19 Jun '26

19 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41178 Bug ID: 41178 Summary: SIP2 module does not notify that linked accounts are deleted when deleting an institution Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: pedro.amorim(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 33

[Bug 31327] New: Can we add color scheme picker to the OPAC.. especially a 'dark mode'?
by bugzilla-daemon＠bugs.koha-community.org 19 Jun '26

19 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31327 Bug ID: 31327 Summary: Can we add color scheme picker to the OPAC.. especially a 'dark mode'? Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org It would be great to support a second or more color scheme on the OPAC.. many apps now have 'dark mode' and 'high contrast'. -- You are receiving this mail because: You are watching all bug changes.

1 40