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

[Bug 17320] New: MySQL 5.7 doesn't work well with SQL using '0000-00-00'
by bugzilla-daemon＠bugs.koha-community.org 18 Dec '20

18 Dec '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17320 Bug ID: 17320 Summary: MySQL 5.7 doesn't work well with SQL using '0000-00-00' Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Installation and upgrade (web-based installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: mtompset(a)hotmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Several SQL statements in updatedatabase.pl have '0000-00-00'. A simple substitution to 0 will prevent a default MySQL 5.7 on Ubuntu from barfing. This patch will touch as far back as 3.0.6, but given the magnitude of other errors while upgrading, finding no 0000-00-00 barfs after the patch up to 3.9 and then finding no 0000-00-00 barfs from 3.14.x upwards seems sufficient to check. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 22

[Bug 16067] New: Koha::Cache, fastmmap caching system is broken
by bugzilla-daemon＠bugs.koha-community.org 17 Dec '20

17 Dec '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16067 Bug ID: 16067 Summary: Koha::Cache, fastmmap caching system is broken Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: abl(a)biblos.pk.edu.pl QA Contact: testopia(a)bugs.koha-community.org After Bug 11998, fastmmap caching system implementation in Koha::Cache ceased to work properly. If fastmmap is enabled (= environment variable CACHING_SYSTEM is set to 'fastmmap'), any CGI script call causes the following error: Use of uninitialized value $db_name in concatenation (.) or string at /home/koha/devkohaclone/Koha/Database.pm line 73. Use of uninitialized value $db_host in concatenation (.) or string at /home/koha/devkohaclone/Koha/Database.pm line 73. DBI connect('database=;host=;port=','',...) failed: Access denied for user 'koha'@'localhost' (using password: NO) at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1249 DBIx::Class::Storage::DBI::dbh(): DBI Connection failed: Access denied for user 'koha'@'localhost' (using password: NO) at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1253. at /home/koha/devkohaclone/Koha/Database.pm line 90 To reproduce on command line: 0) ensure that you have fastmmap perl module installed (libcache-fastmmap-perl in debian) 1) export CACHING_SYSTEM=fastmmap 2) export GATEWAY_INTERFACE=1 3) try to run this simple script: #!/usr/bin/perl use Modern::Perl; use C4::Biblio; GetMarcStructure(); -- You are receiving this mail because: You are watching all bug changes.

1 25

[Bug 17374] New: Make use of fields from syspref ' DefaultPatronSearchFields' in patron search fields dropdown
by bugzilla-daemon＠bugs.koha-community.org 14 Dec '20

14 Dec '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17374 Bug ID: 17374 Summary: Make use of fields from syspref 'DefaultPatronSearchFields' in patron search fields dropdown 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: veron(a)veron.ch QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Bug 14874 introduced syspref 'DefaultPatronSearchFields' to define what fields should be used in default patron search. It would be nice see the fields in the search fields drop down as well. At the moment the are hard coded to: Surname,Email,Borrower number,Username,Phone number,Street Address,Date of birth,Sort field 1,Sort field 2 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 77

[Bug 17268] New: Advanced cataloging editor - rancor - macros are lost when browser storage cleared
by bugzilla-daemon＠bugs.koha-community.org 14 Dec '20

14 Dec '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17268 Bug ID: 17268 Summary: Advanced cataloging editor - rancor - macros are lost when browser storage cleared Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl In development macros were stored in the browser to allow different users to have their own. Unfortunately this means macros are lost when browser storage is cleared. Should have a more robust method for retaining these. -- You are receiving this mail because: You are watching all bug changes.

1 129

[Bug 19351] New: Add Copy number $t in chekout column
by bugzilla-daemon＠bugs.koha-community.org 14 Dec '20

14 Dec '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19351 Bug ID: 19351 Summary: Add Copy number $t in chekout column Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: patrick.robitaille(a)ccsr.qc.ca QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Hi, It would be usefull to see the copy number ($t) in the checkout column. When you are in a user's profil, in the checkout's section you can't see the copy number for items. It will be helpfull to see this informations when in your collection you have many copy number for an item. This information coulb be place in the column Call no? Thanks, Patrick. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 16391] New: In 'Tools', the link 'Tool plugins' has '?method=tool' in its link, which does not show all installed plugins
by bugzilla-daemon＠bugs.koha-community.org 10 Dec '20

10 Dec '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16391 Bug ID: 16391 Summary: In 'Tools', the link 'Tool plugins' has '?method=tool' in its link, which does not show all installed plugins Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Tools Assignee: gmcharlt(a)gmail.com Reporter: arslanone(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org The link for plugins page in 'Tools' labeled as 'Tool plugins' takes us to cgi-bin/koha/plugins/plugins-home.pl?method=tool, see: http://i.imgur.com/ak2T1lE.png But not all installed plugins gets listed that way, see: http://i.imgur.com/ujPNiOZ.png If I manually remove ?method=tool from the address bar, and enter, then I can see all plugins, see: http://i.imgur.com/gH7kB8f.png -- You are receiving this mail because: You are watching all bug changes.

1 11

[Bug 18267] New: Update price and tax fields in EDI to reflect DB changes
by bugzilla-daemon＠bugs.koha-community.org 09 Dec '20

09 Dec '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18267 Bug ID: 18267 Summary: Update price and tax fields in EDI to reflect DB changes Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: colin.campbell(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org The aqorders price and tax fields were renamed/ added to in bug 13321 but the changes were not propagated to EDI.pm which is still creating orders with the prices in the old fields. Update the fields used and check the correct Edifact elements are being assigned -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 58

[Bug 17108] New: Automatic debian/control updates (stable)
by bugzilla-daemon＠bugs.koha-community.org 07 Dec '20

07 Dec '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17108 Bug ID: 17108 Summary: Automatic debian/control updates (stable) Change sponsored?: --- Product: Koha Version: 16.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Packaging Assignee: koha-bugs(a)lists.koha-community.org Reporter: mirko(a)abunchofthings.net QA Contact: testopia(a)bugs.koha-community.org CC: mirko(a)abunchofthings.net -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 64

[Bug 17111] New: Automatic debian/control updates (oldstable)
by bugzilla-daemon＠bugs.koha-community.org 07 Dec '20

07 Dec '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17111 Bug ID: 17111 Summary: Automatic debian/control updates (oldstable) Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Packaging Assignee: koha-bugs(a)lists.koha-community.org Reporter: mirko(a)abunchofthings.net QA Contact: testopia(a)bugs.koha-community.org CC: mirko(a)abunchofthings.net -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 105

[Bug 15791] New: Don't delete a fund if existing orders are linked to it
by bugzilla-daemon＠bugs.koha-community.org 04 Dec '20

04 Dec '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15791 Bug ID: 15791 Summary: Don't delete a fund if existing orders are linked to it Change sponsored?: --- Product: Koha Version: master Hardware: All URL: /cgi-bin/koha/admin/aqbudgets.pl?op=delete_confirm OS: All Status: NEW Severity: normal Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org When you go to delete a fund Koha displays this message in the confirmation dialog: "If you delete this fund, all orders linked to this fund will be deleted!" The error appears even if there are no orders linked to the fund. In order to be consistent we ought to warn the user only if existing orders will be deleted. Should it even be possible to delete a fund if there are orders linked to it? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1