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

[Bug 16721] New: Serial claims table too wide
by bugzilla-daemon＠bugs.koha-community.org 09 Jan '26

09 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16721 Bug ID: 16721 Summary: Serial claims table too wide Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org The serial claims table gets far too wide, especially when new subscription fields are added to it. It should be possible to configure if those display or not, but it also looks like a general problem. -- You are receiving this mail because: You are watching all bug changes.

1 31

[Bug 34164] New: OAuth2/OIDC should redirect to page that initiated login
by bugzilla-daemon＠bugs.koha-community.org 09 Jan '26

09 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34164 Bug ID: 34164 Summary: OAuth2/OIDC should redirect to page that initiated login Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org At the moment, a successful OAuth2/OIDC login is sent to opac-user.pl/opac-main.pl or mainpage.pl instead of the page that initiated the login process. With Shibboleth, we manage this using the "target" URL, so that the Shibboleth login is processed by whatever page initiated it, but that doesn't work with OAuth2/OIDC and the "redirect_uri" since we're using an API endpoint. However, all we need to do is save the current path in the user's session, and then recall it after the successful login. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 43

[Bug 28146] New: admin variable should be replaced by KohaAdminEmailAddress
by bugzilla-daemon＠bugs.koha-community.org 09 Jan '26

09 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28146 Bug ID: 28146 Summary: admin variable should be replaced by KohaAdminEmailAddress Change sponsored?: --- Product: Koha Version: master 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: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org "admin" is sent from C4::Output::output_error, we should use Koha.Preference('KohaAdminEmailAddress') from the template instead koha-tmpl/intranet-tmpl/prog/en/includes/prefs-menu.inc: [% IF ( admin ) %] koha-tmpl/intranet-tmpl/prog/en/modules/errors/errorpage.tt: <li>To report a broken link or any other issue, please contact the Koha Administrator. <a href="mailto:[% admin | uri %]">Send email</a></li> koha-tmpl/opac-tmpl/bootstrap/en/modules/errors/errorpage.tt: <a href="mailto:[% admin | uri %]">Send email</a>.</li> koha-tmpl/opac-tmpl/bootstrap/en/modules/opac-auth.tt: <li>To report this error, you can email the Koha Administrator.<a href="mailto:[% admin | uri %]">Email</a></li> C4/Output.pm: admin => $admin, errors/400.pl: admin => $admin, errors/401.pl: admin => $admin, errors/402.pl: admin => $admin, errors/403.pl: admin => $admin, errors/404.pl: admin => $admin, errors/500.pl: admin => $admin, opac/errors/400.pl: admin => $admin, opac/errors/401.pl: admin => $admin, opac/errors/402.pl: admin => $admin, opac/errors/403.pl: admin => $admin, opac/errors/404.pl: admin => $admin, opac/errors/500.pl: admin => $admin, -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13

[Bug 30102] New: Create a template plugin for library groups
by bugzilla-daemon＠bugs.koha-community.org 08 Jan '26

08 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30102 Bug ID: 30102 Summary: Create a template plugin for library groups Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org In Koha::Template::Plugin::Branches we could add code for library groups. With cache. To at least remove from C4/Auth.pm : my @search_groups = Koha::Library::Groups->get_search_groups({ interface => 'opac' })->as_list; ... LibrarySearchGroups => \@search_groups, -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 30697] New: IsAvailableForItemLevelRequest returns wrong when items_any_available is defined
by bugzilla-daemon＠bugs.koha-community.org 07 Jan '26

07 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30697 Bug ID: 30697 Summary: IsAvailableForItemLevelRequest returns wrong when items_any_available is defined Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: shi-yao.wang(a)inLibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com The IsAvailableForItemLevelRequest subroutine returns wrong value when $items_any_available is defined -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 12

[Bug 31060] New: Fine duplicates when returning item with accountline status marked as lost
by bugzilla-daemon＠bugs.koha-community.org 07 Jan '26

07 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31060 Bug ID: 31060 Summary: Fine duplicates when returning item with accountline status marked as lost Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: shi-yao.wang(a)inLibro.com QA Contact: testopia(a)bugs.koha-community.org To recreate: 1- System preferences: finesMode: Calculate and charge CalculateFinesOnReturn: Do WhenLostChargeReplacementFee: Don't charge MarkLostItemsAsReturned: uncheck from the items tab of the catalog module 2- Have a circulation rule with defined non-zero Fine amount and Fine charging interval. (Will have to use the patron category and item type associated to this circulation rule to test) 3- Checkout a document from the patron with backdated due date (backdated enough depending on the Fine charging interval set) 4- Run ./misc/cronjobs/fines.pl 5- There should be a Fine(Accruing) in accounting tab of the patron 6- Go to the checked out item detail and set Lost status: Long overdue (Lost) and click Set status 7- Now, Fine(Accruing) changed to Fine(Lost) in the accounting tab of the patron 8- In item detail, set Lost status: Choose and click Set status 9- Notice Fine(Lost) did not switch back to Fine(Accruing) in the accounting tab 10- Check in the item 11- Notice there is a duplicate fee Fine(Returned) and Fine(Lost) is still there -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 10

[Bug 17473] New: Reverse payment permission
by bugzilla-daemon＠bugs.koha-community.org 07 Jan '26

07 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17473 Bug ID: 17473 Summary: Reverse payment permission Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: josef.moravec(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com It would be nice to have permission just for reverse payments -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 33

[Bug 34142] New: Add column sub_location to items table
by bugzilla-daemon＠bugs.koha-community.org 07 Jan '26

07 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34142 Bug ID: 34142 Summary: Add column sub_location to items table Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Database Assignee: koha-bugs(a)lists.koha-community.org Reporter: emmi.takkinen(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org We should add new column sub_location to items and deleteditems table. This can be used to indicate e.g. if item has some other more specific location than permanent location. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 47

[Bug 32020] New: Expired pages are still accessible
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '26

06 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32020 Bug ID: 32020 Summary: Expired pages are still accessible Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org When creating a new page with the additional content page, there is a possibility of adding an 'expiration date' to the page, presumably for when the content of the page is not valid anymore. However, the link to that page is still valid after the page has expired. I wonder if the link should return an error page or 404 page or something like that. To test: 1. Go to Tools > Pages > New entry 2. Create a page with no expiry date 4. Access the link to the page in another tab 5. Click 'Edit' next to the page entry 6. Add an expiry date in the past to the entry --> It disappears from the list of pages 7. In the other tab, refresh the page --> It is still accessible -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 31329] New: Add ability to block all linked accounts when one account has been restricted
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '26

06 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31329 Bug ID: 31329 Summary: Add ability to block all linked accounts when one account has been restricted Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com For some libraries, when using guarantor/guarantee relationships, they would like to see that blocks occur on the entire family. For example, if a guarantor/guarantee has been blocked either by an overdue process or a manual restriction- this block would be also placed on the other linked accounts. Once a restriction has been removed, the restrictions on all accounts would be removed. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14