May 2024 - 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 34867] New: Select multiple libraries in Tools (News, HTML customizations and Pages)
by bugzilla-daemon＠bugs.koha-community.org 08 Jan '26

08 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34867 Bug ID: 34867 Summary: Select multiple libraries in Tools (News, HTML customizations and Pages) Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: jzairo(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org In Tools (News, HTML customizations, and Pages) staff can select all libraries or an individual branch. It would be nice if staff could select multiple libraries. Similar to what we do with library limitations in patron categories, authorized values, etc. This would make the creation of News, HTML customizations, and/or Pages easier for large systems, multi-branch, or campuses. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[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 34366] New: Check Previous Checkout blocks on the SCO with no option to checkout anyway
by bugzilla-daemon＠bugs.koha-community.org 07 Jan '26

07 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34366 Bug ID: 34366 Summary: Check Previous Checkout blocks on the SCO with no option to checkout anyway Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Self checkout Assignee: koha-bugs(a)lists.koha-community.org Reporter: lisette.scheer(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org IT would be nice if there was an option for libraries to allow patrons to still check out items that were previously checked out without having to take it to a staff member. Some libraries use the feature as a more informative feature than any sort of restriction. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 35334] New: Give ability to add context to custom Pages in the staff client
by bugzilla-daemon＠bugs.koha-community.org 07 Jan '26

07 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35334 Bug ID: 35334 Summary: Give ability to add context to custom Pages in the staff client 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: jrobb(a)sekls.org QA Contact: testopia(a)bugs.koha-community.org Currently when creating a page for the staff client using the Pages tool, the page gets categorized under Tools which reflects in the breadcrumbs and the left navbar on the page itself. It would be nice if when creating a page for the staff client, one could define the logical context of the custom page and give it the associated breadcrumbs and navbar. As an example, we have a page that curates a list of clean-up reports. Currently the breadcrumbs and left navbar are for "Tools" which is confusing for staff users. It would be helpful if when creating the page we could categorize it as "Reports" so that it would get the breadcrumbs and left nav used within the reports module. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 11