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

[Bug 28019] New: Script "process_message_queue.pl" no more accepting comma separated addresses
by bugzilla-daemon＠bugs.koha-community.org 12 Nov '21

12 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28019 Bug ID: 28019 Summary: Script "process_message_queue.pl" no more accepting comma separated addresses Change sponsored?: --- Product: Koha Version: 20.11 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: mik(a)adminkuhn.ch QA Contact: testopia(a)bugs.koha-community.org Since in the Koha staff client it is not possible to send the same e-mail to two recipients at once we have regularly updated field "message_queue.to_address" of pending messages by SQL to contain two addresses instead of one (e. g. "abc@def.com,xyz@def.com") and in Koha 19.11 script "process_message_queue.pl" sent these notices to both addresses without a problem. But after the update to Koha 20.11 this doesn't work anymore - instead the script says: Invalid 'to' parameter: abc@def.com,xyz@def.comxxx: 11 status returned by "/usr/share/koha/bin/cronjobs/process_message_queue.pl" In Bug 26706 Tomas Cohen Arazi wrote: "The non-advertised feature of accepting comma separated addresses is still not working. I can solve it on a separate bug report if someone files it. It needs to specify which fields could be multi-address." I our case field "message_queue.to_address" did contain two comma separated addresses. According to http://schema.koha-community.org/20_11/tables/message_queue.html this is the only field that contains recipients. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 23194] New: Public notes items in the OPAC should allow for HTML tags
by bugzilla-daemon＠bugs.koha-community.org 12 Nov '21

12 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23194 Bug ID: 23194 Summary: Public notes items in the OPAC should allow for HTML tags Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- As with similar bugs, 22938, 22702, 22501, the HTML tags are broken in the newest version of 18.11. If an item has a URL in the public notes subfield, this should be allowed to have HTML tags. Currently, this is not displaying correctly. -- You are receiving this mail because: You are watching all bug changes.

1 31

[Bug 24224] New: Convert OpacNavBottom system preference to news block
by bugzilla-daemon＠bugs.koha-community.org 11 Nov '21

11 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24224 Bug ID: 24224 Summary: Convert OpacNavBottom system preference to news block Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: testopia(a)bugs.koha-community.org Depends on: 22880 Building on 22318, the OpacNavBottom system preference should be converted to a Koha news block. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22880 [Bug 22880] Convert opacheader system preference to news block -- You are receiving this mail because: You are watching all bug changes.

1 16

[Bug 24674] New: Uncertain years for publicationyear/copyrightdate -- corrected
by bugzilla-daemon＠bugs.koha-community.org 11 Nov '21

11 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24674 Bug ID: 24674 Summary: Uncertain years for publicationyear/copyrightdate -- corrected Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: januszop(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl According to n. 4.3.8 od ISBD Consolidated Edition of 2011, valid for date description are also string like [1960-], [17-]. Currently strings like these are not interpreted correctly by C4::Biblio::_adjust_pubyear. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 43

[Bug 17314] New: REST API: Add API route to create, list and delete a purchase suggestion
by bugzilla-daemon＠bugs.koha-community.org 11 Nov '21

11 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17314 Bug ID: 17314 Summary: REST API: Add API route to create, list and delete a purchase suggestion Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: mail(a)jkozlovsky.cz QA Contact: testopia(a)bugs.koha-community.org It would be nice to have an API for creating a purchase suggestion. It would be used for instance in VuFind. Proposed implementation: To create: POST /suggestions/{borrowernumber} Incoming data: { title (required) author copyrightdate isbn publishercode collectiontitle place itemtype patronreason note negcap } Outcoming data: 200 OK / 403 Forbidden / 409 Conflict (when already exists the proposal) { error status } To list: GET /suggestions/{borrowernumber} Outcoming data: list of suggestions To delete: DELETE /suggestions/{borrowernumber}/{suggestion_id} Outcoming data: 204 No Content (successful deletion) / 403 Forbidden / 404 Not Found -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 135

[Bug 26636] New: New objects.find mojolicious helper
by bugzilla-daemon＠bugs.koha-community.org 11 Nov '21

11 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26636 Bug ID: 26636 Summary: New objects.find mojolicious helper 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: agustinmoyano(a)theke.io Depends on: 26635 Blocks: 8179 We need a new objects.find mojolicious helper, just as objects.search, that enables embedding child objects and authorisation values expansion Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8179 [Bug 8179] Receiving multiple order lines at once https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26635 [Bug 26635] Expand authorised values in REST API call -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 45

[Bug 24183] New: Introduce `before_send_messages` hook
by bugzilla-daemon＠bugs.koha-community.org 11 Nov '21

11 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24183 Bug ID: 24183 Summary: Introduce `before_send_messages` hook Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Plugin architecture Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org It would be beneficial to have a hook inside process_message_queue.pl to allow plugins the option of taking pre-processing actions on the messages in the message queue before they are sent. An example of where this would be beneficial is the Recalls plugin, where currently one has take serverside actions to configure additional cronjobs as part of setting the plugin up. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 26

[Bug 28470] New: Typo: Are you sure you with to chart this report?
by bugzilla-daemon＠bugs.koha-community.org 11 Nov '21

11 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28470 Bug ID: 28470 Summary: Typo: Are you sure you with to chart this report? Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: minor 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 Typo: koha-tmpl/intranet-tmpl/prog/en/modules/reports/guided_reports_start.tt:1392 Fetching full chart data for reports with many rows can cause performance issues. Are you sure you with to chart this report? -- You are receiving this mail because: You are watching all bug changes.

1 12

[Bug 28573] New: Replace authority record with Z39.50/SRU creates new authority record
by bugzilla-daemon＠bugs.koha-community.org 11 Nov '21

11 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28573 Bug ID: 28573 Summary: Replace authority record with Z39.50/SRU creates new authority record Change sponsored?: --- Product: Koha Version: 20.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: sebastian.krieg(a)tuz-eisenach.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com When replacing an authority record with Z39.50/SRU you get a new record and no update of the upgrading record. Test instance: Catalyst IT Ltd. (New Zealand) (https://koha-community.org/demo/) example record: #13 (name: Plato) Steps to reproduce: 1. Menu "Home > Authorities > Details for authority #13 (Personal Name)" 2. Form: https://demo-intra.mykoha.co.nz/cgi-bin/koha/authorities/detail.pl?authid=13 3. Menu "Edit > Replace record via Z39.50/SRU" 4. Field "Name(any)": Homer >> Click "search" 5. choose the second entry "Aschmann, Homer, 1920-" >> click "import" Expected solution: - replace the record #13 with the search data "Aschmann, Homer, 1920-" - Form: https://demo-intra.mykoha.co.nz/cgi-bin/koha/authorities/detail.pl?authid=13 Error: - Menu "Home > Authorities > Adding authority Personal Name" - form: https://demo-intra.mykoha.co.nz/cgi-bin/koha/authorities/authorities.pl?bre… - Save the record as Record #14 - Menu "Home > Authorities > Details for authority #14 (Personal Name)" Note: I found this error in release 21.05., I use a instance 20.11. to reproduce the error. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 29

[Bug 28189] New: Move the base swagger file to YAML
by bugzilla-daemon＠bugs.koha-community.org 11 Nov '21

11 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28189 Bug ID: 28189 Summary: Move the base swagger file to YAML 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: tomascohen(a)gmail.com In order to be able to add better documentation on the API, we should move the base file to YAML, so we can add multi-line Markdown in it. It renders correctly with tools like Redoc. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 25