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

[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 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 20896] New: Move Serial enumeration to the right of callnumber
by bugzilla-daemon＠bugs.koha-community.org 08 Nov '18

08 Nov '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20896 Bug ID: 20896 Summary: Move Serial enumeration to the right of callnumber Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: joy(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Serial Enumeration is typically read together with the item's callnumber. In the staff side, serial enumeration is separated from the callnumber by status, last seen and barcode columns. It would be best if it was directly to the right of the callnumber column. The OPAC does show the callnumber and volume (enumeration) side by side. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 17237] New: Stop koha-create from creating MySQL users without host restriction
by bugzilla-daemon＠bugs.koha-community.org 08 Nov '18

08 Nov '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17237 Bug ID: 17237 Summary: Stop koha-create from creating MySQL users without host restriction Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Packaging Assignee: magnus(a)libriotech.no Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org CC: mirko(a)abunchofthings.net I am trying to tune MySQL using MySQLTuner (http://mysqltuner.com/) When I run it on my Koha server I get a bunch of warnings like this: [!!] User 'koha_x@%' hasn't specific host restriction. [!!] User 'koha_y@%' hasn't specific host restriction. [!!] User 'koha_z@%' hasn't specific host restriction. And in mysql.user I have: | % | koha_x | | % | koha_y | | % | koha_z | | localhost | koha_x | | localhost | koha_y | | localhost | koha_z | The code that creates these users is in koha-create, line 654 an onwards: # Set up MySQL database for this instance. if [ "$op" = create ] then mysql --defaults-extra-file=/etc/mysql/koha-common.cnf <<eof CREATE DATABASE \`$mysqldb\`; CREATE USER \`$mysqluser\`@'$mysql_hostname' IDENTIFIED BY '$mysqlpwd'; CREATE USER \`$mysqluser\`@'%' IDENTIFIED BY '$mysqlpwd'; GRANT ALL PRIVILEGES ON \`$mysqldb\`.* TO \`$mysqluser\`; FLUSH PRIVILEGES; eof fi #` if [ "$op" = use ] then mysql --defaults-extra-file=/etc/mysql/koha-common.cnf --force <<eof CREATE USER \`$mysqluser\`@'$mysql_hostname' IDENTIFIED BY '$mysqlpwd'; CREATE USER \`$mysqluser\`@'%' IDENTIFIED BY '$mysqlpwd'; GRANT ALL PRIVILEGES ON \`$mysqldb\`.* TO \`$mysqluser\`; FLUSH PRIVILEGES; eof fi #` Perhaps it is just a lack of imagination, but I can't really think of a use for the @% unrestricted user. Am I missing something, or can we just get rid of it? Or if they are needed in some scenarios, can we be more clever about when we create unrestricted users, so they are only created when needed? -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 18385] New: Strange display of tabs in subscription details (OPAC)
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '18

06 Nov '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18385 Bug ID: 18385 Summary: Strange display of tabs in subscription details (OPAC) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: veron(a)veron.ch QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Created attachment 61868 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=61868&action=ed… Strange display of tabs in subscription details (OPAC) Tabs do not display correctly in /cgi-bin/koha/opac-serial-issues.pl?biblionumber=nn To reproduce, create a subscription, then display serial in OPAC: Home > Details for [My serial] > Issues for a subscription See screenshot attached. Reproduced with Firefox and IE, same display. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 20521] New: dev installations should run with problematic SQL modes
by bugzilla-daemon＠bugs.koha-community.org 05 Nov '18

05 Nov '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20521 Bug ID: 20521 Summary: dev installations should run with problematic SQL modes Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 20229 So far we have bug 17258 (omnibus to list the issue we have with the new default SQL modes), bug 20144 (which fixed our test suite with these modes) and bug 20229. This last one forces the SQL modes to avoid to modify the DBMS configuration and define the SQL modes we support. We should let developers catch the issues and report/fix them. Also Jenkins must alert us if there is a regression with the test suite. I suggest to enable the problematic SQL modes on dev installs. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20229 [Bug 20229] Remove problematic SQL modes -- You are receiving this mail because: You are watching all bug changes.

1 24

[Bug 17218] New: New list add attempt while logged in as dbadmin should be prevented pre-emptively
by bugzilla-daemon＠bugs.koha-community.org 05 Nov '18

05 Nov '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17218 Bug ID: 17218 Summary: New list add attempt while logged in as dbadmin should be prevented pre-emptively Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Lists Assignee: gmcharlt(a)gmail.com Reporter: indradg(a)l2c2.co.in QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Right now it allows the Koha db admin login to attempt adding a new list. Only while trying to save it does it inform that it is not possible to do so. This is should be made pre-emptive right after the "+ New list" option is clicked. -- You are receiving this mail because: You are watching all bug changes.

1 27

[Bug 18923] New: Resolve a warn in Biblio::GetCOinSBiblio
by bugzilla-daemon＠bugs.koha-community.org 02 Nov '18

02 Nov '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18923 Bug ID: 18923 Summary: Resolve a warn in Biblio::GetCOinSBiblio Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl 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 24