October 2018 - Koha-bugs - lists.koha-community.org

[Bug 21464] New: Overdues export is missing lot of fields
by bugzilla-daemon＠bugs.koha-community.org 09 Nov '18

09 Nov '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21464 Bug ID: 21464 Summary: Overdues export is missing lot of fields Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: major Priority: P5 - low Component: Circulation Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Depends on: 18789 Caused by commit 0ab22e1c7c6b6e8d14a4fb7478ab2a3d42da347d Bug 18789: Send Koha::Patron object to the templates And maybe before Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18789 [Bug 18789] Send a Koha::Patron object to the templates -- You are receiving this mail because: You are watching all bug changes.

1 22

[Bug 21426] New: setting USE_MEMCACHED to "no" in koha-sites.conf does not have any effect
by bugzilla-daemon＠bugs.koha-community.org 09 Nov '18

09 Nov '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21426 Bug ID: 21426 Summary: setting USE_MEMCACHED to "no" in koha-sites.conf does not have any effect Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P3 Component: Installation and upgrade (command-line installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: arouss1980(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org I recently set up a new Koha 18.05 instance for testing and decided not to use memcached. So, in /etc/koha/koha-sites.conf I set the USE_MEMCACHED variable to "no" and ran `koha-create --create-db dev`. Oddly enough, once my instance was up and running I noticed that a memcached process had been started (Home > About Koha in the Staff interface also reported memcached as running). Apparently, setting USE_MEMCACHED to "no" does no longer have any effect because (as of Bug 18342) memcached is enabled by default for new installs. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 23

[Bug 21389] New: Javascript error on article requests page bis
by bugzilla-daemon＠bugs.koha-community.org 09 Nov '18

09 Nov '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21389 Bug ID: 21389 Summary: Javascript error on article requests page bis Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Bug 21076 fixed a Javascript error on article requests page when patron is found. There is also an error when patron is not found, with message : Patron not found No patron with this name, please, try another -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 20941] New: Displaying requests does not display request material type
by bugzilla-daemon＠bugs.koha-community.org 09 Nov '18

09 Nov '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20941 Bug ID: 20941 Summary: Displaying requests does not display request material type Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew.isherwood(a)ptfs-europe.com I'm not sure when this crept in. At some point we switched from storing material type in illrequests.medium to an arbitrary attribute in illrequestattributes. However, the display end of things wasn't updated accordingly. As such, material type doesn't display in any of the UIs, it should! -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 65

[Bug 16420] New: Buttons inconsistent between "Hold found" and "Hold found (waiting)" dialogs in checkin
by bugzilla-daemon＠bugs.koha-community.org 09 Nov '18

09 Nov '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16420 Bug ID: 16420 Summary: Buttons inconsistent between "Hold found" and "Hold found (waiting)" dialogs in checkin 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: jweaver(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com "Hold found": "Confirm hold", "Print slip and confirm" and "Ignore" "Hold found (item is already waiting)": "Confirm", "Cancel hold", "Print and confirm" We should settle on one ordering and wording; the current approach is both bad for translators and confusing for librarians. It's all too easy to reach for the middle button out of muscle memory and cancel a hold! I would argue that the wording and ordering of the "Hold found" dialog is more natural, so the waiting dialog should be changed to the following: "Confirm hold", "Print slip and confirm", "Cancel hold" -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 12

[Bug 21500] New: Warnings in rotating collections
by bugzilla-daemon＠bugs.koha-community.org 09 Nov '18

09 Nov '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21500 Bug ID: 21500 Summary: Warnings in rotating collections Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 11

[Bug 18503] New: Confusing hold and transfer dialog
by bugzilla-daemon＠bugs.koha-community.org 08 Nov '18

08 Nov '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18503 Bug ID: 18503 Summary: Confusing hold and transfer dialog 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: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com To produce the confusing dialog: 1) Place an item belonging to Library A on hold for Patron 1 for pickup at Library B. 2) Trigger hold. Item is now in transit to Library B. 3) Check in item at Library C (item ended up in their hands by mistake). 4) Note 4 buttons. Not clear what to do. Realistically, the hold should be the focus, and sent along with either of the two bottom buttons. The top buttons do not need to be there. Why transfer the item home when it will just continue to trigger the hold? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 19

[Bug 18490] New: Transfer message confusing, cancel button missing
by bugzilla-daemon＠bugs.koha-community.org 08 Nov '18

08 Nov '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18490 Bug ID: 18490 Summary: Transfer message confusing, cancel button missing 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: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When checking in an item that is being transferred to another branch (not for a reserve), the dialog is a bit confusing. It says: Please return item to: Library XYZ And then shows a Print slip button. I see two problems. First, checking in the item initiates the transfer, and this is not clear in the message. Second, you can't cancel the hold unless you check it in again, and then you get the Cancel transfer button. I don't think there is any reason not to show the cancel button the first time around. I also think it would be much clearer as to what is going on if the message read: Transferring item to: Library XYZ I am open to suggestions on the phrasing. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 19551] New: Cash register report has bad erroneous results from wrong order of operations
by bugzilla-daemon＠bugs.koha-community.org 08 Nov '18

08 Nov '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19551 Bug ID: 19551 Summary: Cash register report has bad erroneous results from wrong order of operations Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org in reports/cash_register_stats.pl $whereTType = q{ AND accounttype = 'FOR' OR accounttype = 'W' }; needs parens to combine the OR, better yet: $whereTType = q{ AND accounttype IN ('FOR','W') }; -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 21550] New: DataTables four button pagination uses the wrong icon for disabled buttons
by bugzilla-daemon＠bugs.koha-community.org 08 Nov '18

08 Nov '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21550 Bug ID: 21550 Summary: DataTables four button pagination uses the wrong icon for disabled buttons Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: trivial Priority: P3 Component: Templates Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: arouss1980(a)gmail.com, martin.renvoize(a)ptfs-europe.com, nick(a)bywatersolutions.com, severine.queune(a)bulac.fr, testopia(a)bugs.koha-community.org Depends on: 21506 When four button pagination is used any button which is disabled uses the icon for active buttons. For instance: The "next" button on the last page of results. The arrow icon should be gray instead of blue. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21506 [Bug 21506] DataTables four button pagination uses the wrong icon for First and Last buttons -- You are receiving this mail because: You are watching all bug changes.

1 11