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

[Bug 37787] New: Undocument koha-worker --queue elastic_index
by bugzilla-daemon＠bugs.koha-community.org 03 Feb '25

03 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37787 Bug ID: 37787 Summary: Undocument koha-worker --queue elastic_index Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Documentation for koha-worker --queue elastic_index was added in Bug 36009, and as far as I can tell, that was the right thing to do at the time. Then koha-es-indexer was added in Bug 33108, and after that running both koha-es-indexer and "koha-worker --queue elastic_index" at the same time leads to problems, like only every other elastic_index job getting processed. We should remove the mention of "--queue elastic_index" from the koha-worker docs. (And maybe add a note that only koha-es-indexer should be run.) koha-es-indexer has been introduced to 23.05.00 and 22.11.06, so a fix should not be backported to older versions than that. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20

[Bug 38173] New: Fix description of koha-dump --exclude-indexes
by bugzilla-daemon＠bugs.koha-community.org 03 Feb '25

03 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38173 Bug ID: 38173 Summary: Fix description of koha-dump --exclude-indexes Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Currently: --exclude-indexes Include Zebra indexes on the backup --exclude-logs Exclude /var/log/koha/name from the backup Proposed changes in the first line: --exclude-indexes Exclude Zebra indexes from the backup --exclude-logs Exclude /var/log/koha/name from the backup -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 34920] New: ERM breaks if an ERM authorized value is missing a description
by bugzilla-daemon＠bugs.koha-community.org 03 Feb '25

03 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34920 Bug ID: 34920 Summary: ERM breaks if an ERM authorized value is missing a description Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ERM Assignee: jonathan.druart+koha(a)gmail.com Reporter: Laura.escamilla(a)bywatersolutions.com CC: jonathan.druart+koha(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 To recreate: 1. Enable ERM module 2. Confirm that you can open the ERM module in the staff interface. 3. Go to the authorized values, select "ERM_AGREEMENT_CLOSURE_REASON" and edit the "Cancelled" authorized value by removing the description. Making this change with any of the ERM authorized values will result in an error. 4. Go back to the ERM module and notice that there is an error. "Something went wrong: Error: Expected string - got null." -- You are receiving this mail because: You are watching all bug changes.

1 50

[Bug 38237] New: Add logging to erm_run_harvester cronjob
by bugzilla-daemon＠bugs.koha-community.org 03 Feb '25

03 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38237 Bug ID: 38237 Summary: Add logging to erm_run_harvester cronjob Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 36171] New: Problems with the Russian program interface
by bugzilla-daemon＠bugs.koha-community.org 03 Feb '25

03 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36171 Bug ID: 36171 Summary: Problems with the Russian program interface Change sponsored?: --- Product: Koha Version: 23.11 Hardware: HP OS: Linux Status: NEW Severity: critical Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: sergeinik(a)tut.by QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Created attachment 162490 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=162490&action=e… Russian interface After the last update of the program, the display of user pages, as well as the interface for writing off and adding literature, disappeared in the Russian administrator interface. Everything works in the English interface. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 66

[Bug 38117] New: "Item was not checked in" should not always show
by bugzilla-daemon＠bugs.koha-community.org 03 Feb '25

03 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38117 Bug ID: 38117 Summary: "Item was not checked in" should not always show Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com >From bug 8461 we added the "Item was not checked in" message marked as 'problem' to let users know when item returns were blocked or failed. The message is now showing as well for items that were not checked out, and the problem styling makes staff think there is an issue. We should not show the 'not checked in' message unless the item has a due date/is checked out -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 37178] New: Column "comments" in ILL requests table gives error on sorting, paging cannot be changed
by bugzilla-daemon＠bugs.koha-community.org 03 Feb '25

03 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37178 Bug ID: 37178 Summary: Column "comments" in ILL requests table gives error on sorting, paging cannot be changed Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de CC: pedro.amorim(a)ptfs-europe.com, tomascohen(a)gmail.com Depends on: 36904 The ILL requests table on the front page of the ILL module gives an error when the table is sorted on the column "Comments". There is another error when switching the records per page to any other value than 20. This is from the developer tools: DataTables warning: table id=ill-requests - Ajax error. For more information about this error, please see http://datatables.net/tn/7 datatables_23.1106000.js:467:13 Source map error: Error: request failed with status 404 Resource URL: .../intranet-tmpl/lib/datatables/datatables.min_23.1106000.js Source Map URL: pdfmake.min.js.map GET .../api/v1/ill/requests?_page=1&_per_page=100&_match=contains&_order_by=+me.comments_count REsponse: Internal server error Tested in Koha 23.11, might need confirmation in newer versions. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36904 [Bug 36904] ILL error when searching from table search input -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20

[Bug 38249] New: `koha-list` help typo about elastic
by bugzilla-daemon＠bugs.koha-community.org 03 Feb '25

03 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38249 Bug ID: 38249 Summary: `koha-list` help typo about elastic Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz The script help advertises the `--noelasticsarch` option switch. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14

[Bug 36317] New: Koha::Biblio->host_items fails with search_ordered()
by bugzilla-daemon＠bugs.koha-community.org 03 Feb '25

03 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36317 Bug ID: 36317 Summary: Koha::Biblio->host_items fails with search_ordered() 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: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Koha::Biblio->host_items fails with search_ordered() because of ambiguous column 'itemnumber' in where clause. It must use me.itemnumber like in Koha::Biblio->items -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 34

[Bug 37582] New: SIP2 responses can contain newlines when a patron has multiple debarments
by bugzilla-daemon＠bugs.koha-community.org 03 Feb '25

03 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37582 Bug ID: 37582 Summary: SIP2 responses can contain newlines when a patron has multiple debarments Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org This came up with a SIP vendor recently - when reading responses they were only getting part of a patron's information. It seemed to have been caused by patrons with multiple restrictions and a new line in the response The simple fix was: <screen_msg_regex find="\n" replace=" -- " /> We should possibly add this as an option rather than relying on regex -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 28