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

[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 15504] Track Patron's Last Activity
by bugzilla-daemon＠bugs.koha-community.org 30 Jun '20

30 Jun '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15504 --- Comment #25 from Victor Grousset/tuxayo <victor(a)tuxayo.net> --- Please double check, as a non-native speaker, misunderstandings are bound to happen someday :) (In reply to David Cook from comment #2) > I noticed recently that "lastseen" updates for "Patron logs into OPAC" and > "Patron is authenticated via SIP2" and that's it. I've had libraries > interested in the field being updated for the other activities Nicole > mentioned as well. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 15504] Track Patron's Last Activity
by bugzilla-daemon＠bugs.koha-community.org 30 Jun '20

30 Jun '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15504 --- Comment #24 from Victor Grousset/tuxayo <victor(a)tuxayo.net> --- (In reply to Christopher Brannon from comment #23) > I must be missing something here. Where is the information on patron logins > to OPAC or authentication via SIP2 that isn't in a log? borrowers.lastseen IIUC -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 15504] Track Patron's Last Activity
by bugzilla-daemon＠bugs.koha-community.org 30 Jun '20

30 Jun '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15504 --- Comment #23 from Christopher Brannon <cbrannon(a)cdalibrary.org> --- I must be missing something here. Where is the information on patron logins to OPAC or authentication via SIP2 that isn't in a log? I'm not sure what tables I should be looking at for this information. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 15504] Track Patron's Last Activity
by bugzilla-daemon＠bugs.koha-community.org 30 Jun '20

30 Jun '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15504 --- Comment #22 from Victor Grousset/tuxayo <victor(a)tuxayo.net> --- (In reply to Christopher Brannon from comment #21) > (In reply to Victor Grousset/tuxayo from comment #20) > > > (assuming SQL report are not enough?) > > As was mentioned, pulling stuff from activity logs is hit or miss. I missed that part. What do you mean by activity logs? The issues and old_issues tables? Because if I understand correctly, the following data is in the above tables + borrowers.lastseen > Patron checks out item > Patron renews an item > Patron returns an item > Patron is authenticated via SIP2 > Patron logs into OPAC -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[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 25902] New: Export MARC records for all titles in a virtual shelf
by bugzilla-daemon＠bugs.koha-community.org 30 Jun '20

30 Jun '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25902 Bug ID: 25902 Summary: Export MARC records for all titles in a virtual shelf Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Lists Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl We let user-defined lists / virtual shelves be used to select bibs for record deletion and modification. It would be nice to be able to use a list to export records, too. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4