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

[Bug 35402] Update the OPAC and staff interface to Bootstrap 5
by bugzilla-daemon＠bugs.koha-community.org 03 Sep '24

03 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35402 --- Comment #49 from Jonathan Druart <jonathan.druart(a)gmail.com> --- This patch fixes the failing test and restore the behaviour, but it is not working as intended... -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 35402] Update the OPAC and staff interface to Bootstrap 5
by bugzilla-daemon＠bugs.koha-community.org 03 Sep '24

03 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35402 Jonathan Druart <jonathan.druart(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #170905|0 |1 is obsolete| | --- Comment #48 from Jonathan Druart <jonathan.druart(a)gmail.com> --- Created attachment 170962 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=170962&action=e… Bug 35402: Fix regressions.t The audio alert feature is not correctly designed and is problematic. It looks at the class name in the DOM, not when the element with this class name will be displayed to the end user So it's not possible to make it work for modals for instance, or if an element is built in JS then displayed This patch remove the modal code from the code, if there are no waiting holds. It is the behaviour that existed prior to the Bootstrap update. However it is kind of random behaviour, the song that is played when the librarian open the circ page is different if the user has waiting holds or not. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 33174] New: Have better indication when one is cancelling multiple holds on a record
by bugzilla-daemon＠bugs.koha-community.org 03 Sep '24

03 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33174 Bug ID: 33174 Summary: Have better indication when one is cancelling multiple holds on a record Change sponsored?: --- Product: Koha Version: 22.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation 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 To recreate: 1. Have a record with many holds 2. From request.pl select all the holds and press Cancel seleected(x) 3. A modal popup now appears that says "Are you sure you want to cancel this hold?" 4. It would be nice if this modal more clearly indicated that you are about to cancel many holds. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 21

[Bug 35511] New: Add visual indicators of patron edit form collapsible sections
by bugzilla-daemon＠bugs.koha-community.org 03 Sep '24

03 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35511 Bug ID: 35511 Summary: Add visual indicators of patron edit form collapsible sections Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, koha-bugs(a)lists.koha-community.org, testopia(a)bugs.koha-community.org Depends on: 35510 On the patron add/edit form there is no visible sign that the heading of each section is clickable other than the cursor change. I think adding some style there will help avoid accidentally clicking the heading unintentionally. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35510 [Bug 35510] Non-patron guarantor missing from CollapseFieldsPatronAddForm options -- You are receiving this mail because: You are on the CC list for the bug. You are watching all bug changes.

1 14

[Bug 33511] New: Gather print notices can only send overdue notices to the patron's home library
by bugzilla-daemon＠bugs.koha-community.org 03 Sep '24

03 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33511 Bug ID: 33511 Summary: Gather print notices can only send overdue notices to the patron's home library Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The overdue notices generator can split overdues by home library, so if a patron is from library A and has overdues from libraries A, B and C, that person will receive 3 overdue notices ( one for each library's items ). The problem is, the gather print notices cronjob also has the option to separate notices by branch, but it only works by patron home library. So, with this option enabled, all three overdue notices would by sent to library A. What some libraries are expecting is that the notices for A's items goes to A, B's items goes to B, and so on. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 37811] New: Item details is not displaying the item data
by bugzilla-daemon＠bugs.koha-community.org 03 Sep '24

03 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37811 Bug ID: 37811 Summary: Item details is not displaying the item data Change sponsored?: --- 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: ddvala9(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Created attachment 170954 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=170954&action=e… Screenshot After the update of the Koha version, I consistently encounter an error in the item table at cgi-bin/koha/catalogue/detail.pl?biblionumber=. The item details are not displaying the relevant data, and I have attached a screenshot for reference. The specific error message is: let item_type_description = row._strings.location is undefined. To resolve this issue, I have had to contact a developer who modifies the file through Visual Studio. Once the modification is made, the item details display correctly. If there are any patches or updates that could prevent this error in future version updates, that would be greatly appreciated. Thank you. Dr. Dilipkumar Vala -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 35402] Update the OPAC and staff interface to Bootstrap 5
by bugzilla-daemon＠bugs.koha-community.org 03 Sep '24

03 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35402 Jonathan Druart <jonathan.druart(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |37812 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37812 [Bug 37812] Adjust Vue modals for Bootstrap 5 -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 35794] New: Better docs for switching from Zebra to Elasticsearch
by bugzilla-daemon＠bugs.koha-community.org 03 Sep '24

03 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35794 Bug ID: 35794 Summary: Better docs for switching from Zebra to Elasticsearch Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org The documentation around the SearchEngine syspref bsically says "Use following search engine [Zebra|Elasticsearch]", both in the manual and in the syspref interface: https://koha-community.org/manual/latest/en/html/administrationpreferences.… But in order for things to work properly there are at least a couple of things that need to be started on the server: - koha-es-indexer - koha-worker --queue elastic_index This might be documented somewhere that I am be missing, but I think there should be at least a hint about these things both in the manual and in the syspref interface. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 19518] New: Document per-site .psgi files
by bugzilla-daemon＠bugs.koha-community.org 03 Sep '24

03 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19518 Bug ID: 19518 Summary: Document per-site .psgi files Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: magnus(a)libriotech.no Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org koha-plack uses /etc/koha/plack.psgi by default, but it can also use /etc/koha/sites/${instancename}/plack.psgi if one is present. This should be documented in the manpage of koha-plack and the usage embedded in the script. -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 37798] New: Koha About reporting that Elasticsearch is "not running" but it is
by bugzilla-daemon＠bugs.koha-community.org 02 Sep '24

02 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37798 Bug ID: 37798 Summary: Koha About reporting that Elasticsearch is "not running" but it is Change sponsored?: --- Product: Koha Version: 24.05 Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org I've been able to confirm this in Koha 24.05, I haven't looked at other versions. I've spun up KTD with ES7 and the About page is reporting "Version: | Nodes: | Status: not running" for Elasticsearch, even though the SearchEngine syspref is set correctly, and searching and indexing is working. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3