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

[Bug 8137] Checkout limit for all libraries
by bugzilla-daemon＠bugs.koha-community.org 05 Oct '26

05 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8137 Lisette Scheer <lisette(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Signed Off |Failed QA QA Contact|testopia(a)bugs.koha-communit |lisette(a)bywatersolutions.co |y.org |m --- Comment #172 from Lisette Scheer <lisette(a)bywatersolutions.com> --- The warning for the checkout doesn't specify that it's from the global limit, it just looks like a matching rule from the global. The only difference on the message when the global limit is set is that it's for all libraries, but it's confusing for troubleshooting that it doesn't specify that it's the global limit. Too many checked out. 5 checked out, only 5 are allowed. Maximum checkouts calculated from the circulation rule for Item type: All item types Patron category: All patron categories Library: Centerville I tried adding another if to the list after the library: [% IF rule.has_prority == "1" %] <li> Global checkout limit </li> [% END %] But I get the following error when I try checking an item out: Template process failed: undef error - The method Koha::CirculationRule->has_prority is not covered by tests! Trace begun at /kohadevbox/koha/Koha/Object.pm line 1057 Koha::Object::AUTOLOAD('Koha::CirculationRule=HASH(0x55ecbcfd7538)') called at /kohadevbox/koha/koha-tmpl/intranet-tmpl/prog/en/modules/circ/circulation.tt line 1385 This is what gets dumped out if you dump the rule: $VAR1 = { 'rule_name' => 'maxissueqty', 'categorycode' => undef, 'branchcode' => undef, 'rule_value' => '5', 'itemtype' => undef, 'has_priority' => 1, 'id' => 54 }; This pointed out to me that we should have tests to cover this use case. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 16291] New: koha-remove --purge should also delete /etc/koha/sites/instance
by bugzilla-daemon＠bugs.koha-community.org 05 Oct '26

05 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16291 Bug ID: 16291 Summary: koha-remove --purge should also delete /etc/koha/sites/instance Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Tools Assignee: gmcharlt(a)gmail.com Reporter: mtj(a)kohaaloha.com QA Contact: testopia(a)bugs.koha-community.org It would be useful if 'koha-remove --purge' also deleted a /etc/koha/sites/instance dir -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 24237] New: The 406 response on the biblios end point should be more discoverable
by bugzilla-daemon＠bugs.koha-community.org 05 Oct '26

05 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24237 Bug ID: 24237 Summary: The 406 response on the biblios end point should be more discoverable Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com Other endpoints default to an application/json response by default regardless of the Accept headers in the request. For consistency, we should do the same on the biblios endpoint.. I'm thinking a 406 still, but with a JSON encoded error message in the body explaining the available Accept headers. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 32454] New: Patron do not have Overdue Triggers format choice
by bugzilla-daemon＠bugs.koha-community.org 05 Oct '26

05 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32454 Bug ID: 32454 Summary: Patron do not have Overdue Triggers format choice Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org Unlike most other notifications, patrons do not get to define what format they receive overdue notices. So, if a library offers all formats, the patron will get all formats, provided they have the address/phone number needed. Why these notices are handled differently from other notices, I do not know, but it would be nice if patrons had a choice in how they get these notices. If it is a matter of them getting always getting a notice, perhaps one format should be on by default and not changeable unless they have the required elements for another delivery format. Having a global setting for patrons on overdues is not patron friendly. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 38291] New: Add GET /library_groups
by bugzilla-daemon＠bugs.koha-community.org 05 Oct '26

05 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38291 Bug ID: 38291 Summary: Add GET /library_groups Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: matt.blenkinsop(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com We should have an endpoint to list library groups -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 48

[Bug 28957] Many plugins require the full plugins permission set to run
by bugzilla-daemon＠bugs.koha-community.org 05 Oct '26

05 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28957 --- Comment #15 from Lisette Scheer <lisette(a)bywatersolutions.com> --- The demo plugin would be super helpful! -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 43726] New: Make it easy to add html/text to additional contents locations from a plugin
by bugzilla-daemon＠bugs.koha-community.org 05 Oct '26

05 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43726 Bug ID: 43726 Summary: Make it easy to add html/text to additional contents locations from a plugin Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: lisette(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Similar to the intranet_js option in the plugins, having an easy way to insert into additional contents. We could potententially just do it as an "insert into additional_contents" sql, but then it would be editable, which might not be what we want all the time. being able to do something like: reports_home ( <p>This is a paragraph</p> ); and have it just insert that where the additional contents for reports_home goes, would be really handy. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 39350] New: The language switch is not displayed at the bottom of ERM module pages
by bugzilla-daemon＠bugs.koha-community.org 05 Oct '26

05 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39350 Bug ID: 39350 Summary: The language switch is not displayed at the bottom of ERM module pages Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: ERM Assignee: jonathan.druart(a)gmail.com Reporter: mathsabypro(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: jonathan.druart(a)gmail.com, jonathan.field(a)ptfs-europe.com, martin.renvoize(a)ptfs-europe.com, matt.blenkinsop(a)ptfs-europe.com, pedro.amorim(a)ptfs-europe.com If the staff interface is available in several language, a langage switch is displayed at the bottom ok Koha's page (id=i18nMenu). It is not displayed at the bottom of ERM pages -- You are receiving this mail because: You are watching all bug changes.

1 18

[Bug 34671] New: Collapsing fields in patron form allows saving without mandatory fields
by bugzilla-daemon＠bugs.koha-community.org 05 Oct '26

05 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34671 Bug ID: 34671 Summary: Collapsing fields in patron form allows saving without mandatory fields Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: emmi.takkinen(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com We've had cases where user has been able to save patron without address. It turned out that if one collapses patron entry fields validating those fields no longer works even if they are marked as mandatory. To reproduce: 1. Make sure you have "Main address" fields set as mandatory with BorrowerMandatoryField syspref (address, city, zipcode) 2. Add new patron, fill in some info, but leave "Main address" fields empty. 3. Attempt to save. => "This field is mandatory" should be displayed next to the address fields. 4. Collapse "Main address" section. 5. Attempt to save again. => Patron is saved successfully without address information. I'm using address section as an example here, but this happens with every other fields as well. I was able to save patron without surname and date of birth this way. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 62

[Bug 10188] Top Most-circulated items doesn't count current loans
by bugzilla-daemon＠bugs.koha-community.org 05 Oct '26

05 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10188 Cab Vinton <bibliwho(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|bibliwho(a)gmail.com | -- You are receiving this mail because: You are watching all bug changes.

1 0