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

[Bug 22600] New: We should add an 'interface' field to accountlines
by bugzilla-daemon＠bugs.koha-community.org 29 Jul '20

29 Jul '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22600 Bug ID: 22600 Summary: We should add an 'interface' field to accountlines Change sponsored?: --- Product: Koha Version: master 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Prior to bug 22008 we were defaulting to a manager_id of '0' wherever we found a userenv was not set. This roughly equated to signifying that an action had taken place via a script of cronjob... however I'm not sure I saw this behaviour documented anywhere. With bug 22008 adding constraints to manager_id it highlighted this behaviour and raised the question as to how we should overcome it. I believe the clearest approach to identifying 'where' an action has taken place would be to add an interface field to the accountlines table and set it for any action. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 63

[Bug 20355] New: Add example column to administration currency table
by bugzilla-daemon＠bugs.koha-community.org 28 Jul '20

28 Jul '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20355 Bug ID: 20355 Summary: Add example column to administration currency table Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: josef.moravec(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com It would be nice to have this column to ensure you set the right settings for each currency defined. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 24251] New: Patron modification logs should be ordered most recent first
by bugzilla-daemon＠bugs.koha-community.org 28 Jul '20

28 Jul '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24251 Bug ID: 24251 Summary: Patron modification logs should be ordered most recent first Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com The ordering of the patron modification logs seems wrong, surely one is most interested in the most recent modifications and working backwards through the logs? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 23587] New: Advanced search (staff) - list navigation breaks after detailed view
by bugzilla-daemon＠bugs.koha-community.org 28 Jul '20

28 Jul '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23587 Bug ID: 23587 Summary: Advanced search (staff) - list navigation breaks after detailed view Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: claes.eriksson(a)vti.se QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com 1. Advanced search in staff client: make a search that retrieve at least 4 pages with results 2. Navigate to the bottom of page 2 and open detailed view for the last result on the page 3. Click the Next button 4. You should now see detailed view of the first result on page 3. The bug is that you are sent to the first result on page 2. RESET This is a only to show that it does not seem to matter if you in step 2 goes to page 2,3,4 or whatever. You will in step 4 always end up viewing the detailed view of the first result on page 2 1. Advanced search in staff client: make a search that retrieve at least 4 pages with results 2. Navigate to the bottom of page 3 and open detailed view for the last result on the page 3. Click the Next button 4. You should now see detailed view of the first result on page 4. The bug is that you are sent to the first result on page 2. Tested in 18.11 and 17.11. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 23382] New: Hourly rental fees are not charged
by bugzilla-daemon＠bugs.koha-community.org 28 Jul '20

28 Jul '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23382 Bug ID: 23382 Summary: Hourly rental fees are not charged Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major 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 To recreate: 1 - Define an hourly rental fee for an item type, and set it's circ rule to hourly units 2 - Check out an item of that type 3 - Nothing is charged 4 - Enable RentalFeesCheckoutConfirmation syspref 5 - Checkout another item of that type 6 - Note you are notified of the correct charge 7 - Note that confirmation does not charge -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 98

[Bug 20468] New: Multiselect on staff article requests form
by bugzilla-daemon＠bugs.koha-community.org 27 Jul '20

27 Jul '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20468 Bug ID: 20468 Summary: Multiselect on staff article requests form Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 38

[Bug 24363] New: Datepicker calendar is not sexy on additem.pl
by bugzilla-daemon＠bugs.koha-community.org 24 Jul '20

24 Jul '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24363 Bug ID: 24363 Summary: Datepicker calendar is not sexy on additem.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 96893 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=96893&action=ed… Screenshot showing the date acquired field in additem I just wanted to mention that the datepicker calendar icon looks weird in the additem form (probably elsewhere too). Could we make it bigger and centered? Also the ellipsis (...) is not next to the box as it was before. -- You are receiving this mail because: You are watching all bug changes.

1 59

[Bug 24352] New: OpacItemLocation is buggy
by bugzilla-daemon＠bugs.koha-community.org 24 Jul '20

24 Jul '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24352 Bug ID: 24352 Summary: OpacItemLocation is buggy 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org The different settings from the OpacItemLocation don't appear to work correctly. When "collection" is selected, collection is not visible, but a label 'Location(s)' shows up? The callnumber never showed for me in my testing? -- You are receiving this mail because: You are watching all bug changes.

1 32

[Bug 21067] New: Under plack, 500 errors only show as "Internal Server Error"
by bugzilla-daemon＠bugs.koha-community.org 23 Jul '20

23 Jul '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21067 Bug ID: 21067 Summary: Under plack, 500 errors only show as "Internal Server Error" Change sponsored?: --- Product: Koha Version: master 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: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When plack is not running, 500 errors will show the error message of the perl file where the error occurred, as well as a contact email address, something like this: 500 Internal Server Error Use of uninitialized value within @itemnumber in string ne at /usr/share/koha/intranet/cgi-bin/reserve/modrequest.pl line 70. To report a broken link or any other issue, please contact the Koha Administrator. (I think the text is actually from koha-tmpl/intranet-tmpl/prog/en/modules/errors/errorpage.tt) Under plack, all we see is Internal Server Error This means that a) Errors are less likely to be reported to the server administrator because there's no mailto. b) We can't immediately see the error message when the error is reported. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 20437] New: Force requirement for HTTP::OAI 3.27
by bugzilla-daemon＠bugs.koha-community.org 23 Jul '20

23 Jul '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20437 Bug ID: 20437 Summary: Force requirement for HTTP::OAI 3.27 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Packaging Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: mirko(a)abunchofthings.net Until HTTP::OAI is patched so it actually works, and bug 17704 fixes the API change Koha-side, we need to explicitly pull the right version. Otherwise people using Debian 9+ derived distros (Ubuntu 16.04+) are seeing production issues. This implies packaging our custom libhttp-oai-perl distribution in the meantime. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 25