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

[Bug 21455] New: Authority search options get shuffled around when you click on 'Search'
by bugzilla-daemon＠bugs.koha-community.org 08 Nov '18

08 Nov '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21455 Bug ID: 21455 Summary: Authority search options get shuffled around when you click on 'Search' Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: arouss1980(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org As per the attached screenshots, when you perform an authority search in the staff client and click on the 'Search' button, the selected values for the 'Search all headings:' and 'Search entire record:' options get flipped around. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 21752] New: request.pl does not allow to revert Waiting to Priority 1
by bugzilla-daemon＠bugs.koha-community.org 08 Nov '18

08 Nov '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21752 Bug ID: 21752 Summary: request.pl does not allow to revert Waiting to Priority 1 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Hold requests 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 Bug 21611 fixes a problem with the priority status, but full functionality is not restored. If an item is marked as waiting, there is NO WAY to set it back to a priority level. To test: 1) Place item on hold. 2) Check in the item to trigger the hold. 3) Look at requests.pl. Note waiting status. 4) Try to set to priority 1 instead of waiting. You can't. Can only delete. 5) Place another hold on the same item with another patron. 6) Look at requests.pl. Note one waiting status and one priority 1 status. 7) Note that priority 1 is now an option on the waiting hold, but you can't select it! Expected behavior: Change waiting status to priority 1. If there is more than one hold, change it to whatever hold level needed, and bump the rest of the priorities below that accordingly. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 21611] New: Priority in request.pl shows 1 instead of Waiting
by bugzilla-daemon＠bugs.koha-community.org 08 Nov '18

08 Nov '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21611 Bug ID: 21611 Summary: Priority in request.pl shows 1 instead of Waiting Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Hold requests 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 To test: 1) Place and item on hold. 2) Trigger the hold. 3) Go to request.pl. Notice that priority shows "1" rather than "Waiting", even though it shows as waiting in the Pickup library column. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 21435] New: Switch two-column templates to Bootstrap grid: Tools part 3
by bugzilla-daemon＠bugs.koha-community.org 08 Nov '18

08 Nov '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21435 Bug ID: 21435 Summary: Switch two-column templates to Bootstrap grid: Tools part 3 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: testopia(a)bugs.koha-community.org Blocks: 20654 These two-column tools templates can be updated to use the Bootstrap grid. - tools/marc_modification_templates.tt - tools/modborrowers.tt - tools/overduerules.tt - tools/picture-upload.tt - tools/quotes-upload.tt - tools/quotes.tt Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20654 [Bug 20654] Omnibus: Update two-column templates to use Bootstrap grid -- You are receiving this mail because: You are watching all bug changes.

1 8

[Bug 21434] New: Switch two-column templates to Bootstrap grid: Tools part 2
by bugzilla-daemon＠bugs.koha-community.org 08 Nov '18

08 Nov '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21434 Bug ID: 21434 Summary: Switch two-column templates to Bootstrap grid: Tools part 2 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: testopia(a)bugs.koha-community.org Blocks: 20654 These two-column tools templates can be updated to use the Bootstrap grid. - tools/export.tt - tools/holidays.tt - tools/import_borrowers.tt - tools/inventory.tt - tools/manage-marc-import.tt Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20654 [Bug 20654] Omnibus: Update two-column templates to use Bootstrap grid -- You are receiving this mail because: You are watching all bug changes.

1 14

[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 9968] Incorrect index used for 'Standard number' in advanced search
by bugzilla-daemon＠bugs.koha-community.org 08 Nov '18

08 Nov '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9968 Fridolin SOMERS <fridolin.somers(a)biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fridolin.somers(a)biblibre.co | |m --- Comment #10 from Fridolin SOMERS <fridolin.somers(a)biblibre.com> --- Pushed to 17.11.x for 17.11.12 -- You are receiving this mail because: You are watching all bug changes.

1 0

[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 11529] Add subtitle, medium and part fields to biblio table
by bugzilla-daemon＠bugs.koha-community.org 08 Nov '18

08 Nov '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11529 Ere Maijala <ere.maijala(a)helsinki.fi> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Add subtitle field to |Add subtitle, medium and |biblio table |part fields to biblio table -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 11529] Add subtitle field to biblio table
by bugzilla-daemon＠bugs.koha-community.org 08 Nov '18

08 Nov '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11529 --- Comment #22 from Ere Maijala <ere.maijala(a)helsinki.fi> --- With the latest patches e.g. holds reports in circulation display the information properly. -- You are receiving this mail because: You are watching all bug changes.

1 0