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

[Bug 23276] New: Don't show tags on tag cloud when tagging is disabled
by bugzilla-daemon＠bugs.koha-community.org 02 Jul '20

02 Jul '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23276 Bug ID: 23276 Summary: Don't show tags on tag cloud when tagging is disabled Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org When tagging is disabled, Koha still lets you acces the tags cloud page. It displays a message that tagging is disabled, but at the same time tags in the system are displayed: .../cgi-bin/koha/opac-tags.pl I think we should handle this like other pages and not have this page accessible when the feature is diabled. But at least we shoudl not show tags, that might have been added for testing the feature. -- You are receiving this mail because: You are watching all bug changes.

1 30

[Bug 25327] New: Cannot access API spec
by bugzilla-daemon＠bugs.koha-community.org 02 Jul '20

02 Jul '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25327 Bug ID: 25327 Summary: Cannot access API spec Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com On matser, when I try to visit the API spec: http://localhost:8080/api/v1/.html http://localhost:8081/api/v1/.html I get an error: error "Authentication failure." -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 24

[Bug 24003] New: REST API basic auth lacks C4::Context->userenv
by bugzilla-daemon＠bugs.koha-community.org 02 Jul '20

02 Jul '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24003 Bug ID: 24003 Summary: REST API basic auth lacks C4::Context->userenv Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST api Assignee: koha-bugs(a)lists.koha-community.org Reporter: lari.taskula(a)hypernova.fi -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 56

[Bug 23192] New: Cancelling holds over returning to wrong tabon waitingreserves.pl
by bugzilla-daemon＠bugs.koha-community.org 02 Jul '20

02 Jul '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23192 Bug ID: 23192 Summary: Cancelling holds over returning to wrong tabon waitingreserves.pl Change sponsored?: --- Product: Koha Version: master 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 Target Milestone: --- Bug 21628 moved the tables to an include, however, it didn't take the 'tab' input into account To recreate: 1 - Place a hold 2 - Confirm the hold 3 - In the db change the expiration date: UPDATE reserves SET expirationdate = '2019-01-01'; 4 - Go to Home->Circulation->Holds awaiting pickup 5 - View your holds on the 'Holds waiting over' tab 6 - Inspect the button, note tab = "holdswaiting" -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 24668] New: Allow users to specify in plugins how often to run the plugin's cron
by bugzilla-daemon＠bugs.koha-community.org 02 Jul '20

02 Jul '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24668 Bug ID: 24668 Summary: Allow users to specify in plugins how often to run the plugin's cron Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Plugin architecture Assignee: koha-bugs(a)lists.koha-community.org Reporter: wizzyrea(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 20897 as an extension of bug 20897, it would be nice for plugin authors to be able to specify when to run a cron. One way to do it might be to have minute, hourly, and daily default crons, and they each check for the timing flag in the plugin config. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20897 [Bug 20897] Add generic cronjob to run plugins with a 'cronjob' method -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 20897] New: Add generic cronjob to run plugins with a 'cronjob' method
by bugzilla-daemon＠bugs.koha-community.org 02 Jul '20

02 Jul '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20897 Bug ID: 20897 Summary: Add generic cronjob to run plugins with a 'cronjob' method Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement 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 Sometimes there are ad-hoc cronjobs that need to be setup for a site, or there are plugins that need some regular tasks done. I was thinking an easy solution might be to package a generic cronjob into koha that would run daily (or whenever) to check for plugins with a cronjob method. The plugins could allow for configuration of the job in their configure method so that users could have control over some jobs. Could be used for emailing reports or other things that might benefit from a user facing solution. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 11

[Bug 19508] New: When returning a lost item, Koha claim to have applied a refund when it has not
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '20

01 Jul '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19508 Bug ID: 19508 Summary: When returning a lost item, Koha claim to have applied a refund when it has not Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com 1) Create a new item 2) Set it to 'missing' from the edit item screen (you might have to change the visibility setting of this subfield in order to do that) 3) Return the item 4) Verify that Koha reports: A refund has been applied to the borrowing patron's account. This message should only be shown, when an actual refund has been applied. It would also be nice to link to the patron in question in the message. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 23707] New: Z39.50 import goes to Basic Editor, even when Advanced editor is enabled
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '20

01 Jul '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23707 Bug ID: 23707 Summary: Z39.50 import goes to Basic Editor, even when Advanced editor is enabled Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: hayleymapley(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When the EnableAdvancedCatalogingEditor is set to enabled, I expect that Z39.50 import in the Cataloguing module would take you into the Advanced Editor, as the Advanced Editor and New record buttons do. Here is what I think is expected: https://koha-community.org/manual/19.05/en/html/cataloging.html#advanced-ed… -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 24862] New: REST API throws 500 errors for browser after logout
by bugzilla-daemon＠bugs.koha-community.org 30 Jun '20

30 Jun '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24862 Bug ID: 24862 Summary: REST API throws 500 errors for browser after logout Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au It looks like the REST API might not be handling cookies correctly. To test: 0. Use koha-testing-docker 1. Login to http://localhost:8080/ 2. Go to http://localhost:8080/api/v1/libraries 3. Observe a 200 OK HTTP code and JSON output 4. Logout from http://localhost:8080/ 5. Go to http://localhost:8080/api/v1/libraries 6. Observe a 500 Internal Server Error and the following JSON output: {"error":"Something went wrong, check the logs."} It seems to me that really that should be returning a 401 and the following JSON output: {"error":"Authentication failure."} -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 22

[Bug 22167] New: Allow itemnumber column to be labelled differently when using bach item edit feature
by bugzilla-daemon＠bugs.koha-community.org 30 Jun '20

30 Jun '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22167 Bug ID: 22167 Summary: Allow itemnumber column to be labelled differently when using bach item edit feature Change sponsored?: --- Product: Koha Version: 17.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Bug 19233 added a feature that allows you to send a list of items to the item batch edit from a saved SQL report. At the moment this only works, if your column is displayed as itemnumber. Example: Works: show itemnumber from items; Doesn't work: show itemnumber as "Item#" from items; This is not nice for translations. It would be nice if there was a different way to mark the itemnumber and explicitly activate the feature. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6