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

[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

[Bug 8855] Link from receipt to invoice
by bugzilla-daemon＠bugs.koha-community.org 02 Sep '24

02 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8855 --- Comment #7 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- I realize there was some confusion, this patch already has proper attribution. Please disregard the last comment. -- 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 02 Sep '24

02 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| |37807 --- Comment #47 from Jonathan Druart <jonathan.druart(a)gmail.com> --- (In reply to Jonathan Druart from comment #29) > (In reply to Jonathan Druart from comment #28) > > 2. > > # Failed test 'Update child to patron' > > # at t/db_dependent/selenium/update_child_to_adult.t line 153. > > Error while executing command: unexpected alert open: Dismissed user prompt > > dialog: Are you sure you want to update this child to an Adult category? > > This cannot be undone. at /usr/share/perl5/Selenium/Remote/Driver.pm line > > 411. > > > > This is happening because the "Update child to adult" item in the "More" > > menu (members module) is clickable. There is a tooltip and prior to this > > change the item was not clickable and we didn't get the alert. > > Related to this, it seems that the next entry "Export today's checked in > barcodes" is not shown and disabled when needed. We certainly want this > change: > > [% IF Koha.Preference('intranetreadinghistory') %] > - [%IF ( privacy == 2 ) %] > + [%IF ( patron.privacy == 2 ) %] Opened bug 37807. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37807 [Bug 37807] "Export today's checked in barcodes" not disabled when needed -- 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 02 Sep '24

02 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35402 --- Comment #46 from Jonathan Druart <jonathan.druart(a)gmail.com> --- (In reply to Jonathan Druart from comment #45) > It fixes the test but it is a change in the behaviour. Prior to this > patchset, beep was played. Now it's opening. > It happens because we have the modal in the DOM, and it has the > 'audio-alert-action' class. And opening is not played when it should: Turn on WaitingNotifyAtCheckout Place a hold and checkin barcode_1 (waiting hold) checkout barcode_2 => modal is displayed ("This patron has waiting holds"), but nothing played. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14250] Don't allow to generate discharges for patrons with fines
by bugzilla-daemon＠bugs.koha-community.org 02 Sep '24

02 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14250 --- Comment #32 from Baptiste Wojtkowski (bwoj) <baptiste.wojtkowski(a)biblibre.com> --- (In reply to Katrin Fischer from comment #31) > As the both text blocks appear to be added by this patch set - could we > reuse the same text block for both, defined in one spot? Hum.. Yes I tried to focus on the change needed. I think the page needs a cleanup out from this scope. The business of the function was quite messy, with multiple variables containing the same information but for different purposes (for example has_issues and has_checkout do not have the same content according to the fact the user can or cannot be discharged). In a first while, we should probably use two different texts, one referring to the fact that the user cannot ask for a discharge and one referring to the fact that user's state has changed between the load of the page and the click on the discharge button (but tbh I don't know if anyone will see it). In a second while, I'll submit a separate patch to de-duplicate variables and clean the function itself. I think this will be easier to track the changes so. Does this solution looks fine for you ? -- You are receiving this mail because: You are watching all bug changes.

1 0