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

[Bug 32172] New: Random biblionumber passed when clicking 'Z3950 SRU/Search' from the search results in staff client
by bugzilla-daemon＠bugs.koha-community.org 23 Sep '23

23 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32172 Bug ID: 32172 Summary: Random biblionumber passed when clicking 'Z3950 SRU/Search' from the search results in staff client Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Staff Client 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 The code for Z3950 popup: 393 /* this function open a popup to search on z3950 server. */ 394 function PopupZ3950() { 395 if( strQuery ){ 396 window.open("/cgi-bin/koha/cataloguing/z3950_search.pl?biblionumber=" + biblionumber + strQuery,"z3950sear ch",'width=740,height=450,location=yes,toolbar=no,scrollbars=yes,resize=yes'); 397 } 398 } 399 Picks a random biblionumber variable Seems to get defined when images are enabled, presumably from verify_cover_images We shouldn't ever be replacing a biblio from the results page, so lets just remove it -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 14825] Accounts Rewrite Omnibus
by bugzilla-daemon＠bugs.koha-community.org 23 Sep '23

23 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14825 Bug 14825 depends on bug 22510, which changed state. Bug 22510 Summary: 'accountlines.accounttype' should never be set directly, rather is should be changed via Koha::Account et al. https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22510 What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 22510] New: 'accountlines.accounttype' should never be set directly, rather is should be change via Koha::Account et al.
by bugzilla-daemon＠bugs.koha-community.org 23 Sep '23

23 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22510 Bug ID: 22510 Summary: 'accountlines.accounttype' should never be set directly, rather is should be change via Koha::Account et al. 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: --- Koha::Account lists valid value for accounttypes which can be added via the methods add_debit and add_credit. However, we're still setting accounttype in a number of places outside of this module and in many cases the values we're using do not correspond to the enum list in Koha::Account. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19

[Bug 22506] New: Transfer Slip does not populate on branchtransfers.pl
by bugzilla-daemon＠bugs.koha-community.org 23 Sep '23

23 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22506 Bug ID: 22506 Summary: Transfer Slip does not populate on branchtransfers.pl 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: jzairo(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Target Milestone: --- It would be beneficial for some libraries who are transferring items from branch A to branch B to have a transfer slip to include with the transfer. Currently when a user is on branchtransfers.pl and enters a barcode to transfer an item to another branch, no transfer slip populates. It would be great to have the TRANSFERSLIP populate and have the option to print. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 11151] hold error message wrong if in transit
by bugzilla-daemon＠bugs.koha-community.org 23 Sep '23

23 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11151 Emily Lamancusa <emily.lamancusa(a)montgomerycountymd.gov> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |emily.lamancusa@montgomeryc | |ountymd.gov --- Comment #4 from Emily Lamancusa <emily.lamancusa(a)montgomerycountymd.gov> --- Is this still valid? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 22840] New: Force insert of mandatory data
by bugzilla-daemon＠bugs.koha-community.org 23 Sep '23

23 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22840 Bug ID: 22840 Summary: Force insert of mandatory data Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Installation and upgrade (command-line installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- During the installation process there is a "mandatory" data that can be unchecked. If some are unchecked, Koha will certainly not work as expected, we may want to force the insert of these .sql file (like sysprefs, notices, AV, etc.) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 22817] New: Call viewlog.pl using GET rather than POST
by bugzilla-daemon＠bugs.koha-community.org 23 Sep '23

23 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22817 Bug ID: 22817 Summary: Call viewlog.pl using GET rather than POST Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- When in the log viewer, the page uses POST rather than GET. This means that the HTTP params are not viewable in the address bar. This is very inconvenient from a support standpoint, since you can't then copy the URL from the address bar in order to show someone what you're seeing in the logs -- instead, you have to tell them what to look for in the logs, which is very error prone. Possibly even better would be a 'Copy URL' button. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 22810] New: Item batch mod fails when itype description contains a comma
by bugzilla-daemon＠bugs.koha-community.org 23 Sep '23

23 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22810 Bug ID: 22810 Summary: Item batch mod fails when itype description contains a comma Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Target Milestone: --- Confirmed this behavior in 18.05 and 18.11. To test: - Create an itype with a comma in its description - Create items without an itype - Put those items into item batch modification - Attempt to set items to your new itype - Koha will return "No items were modified" and the itype will remain null This only occurs when items have a null itype. Batch mod can correctly set an item to an itype with a comma in the description if that item is starting from a non-null itype. This only occurs in batch modification. Item creation and single item edits work correctly with itypes with a comma in the description. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 22805] New: When borrowers.dateofbirth is set to a date matching '0YYY-MM-DD', memberentry.pl crashes on save.
by bugzilla-daemon＠bugs.koha-community.org 23 Sep '23

23 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22805 Bug ID: 22805 Summary: When borrowers.dateofbirth is set to a date matching '0YYY-MM-DD', memberentry.pl crashes on save. Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Target Milestone: --- Symptom: Crash on save when in memberentry.pl for a particular patron. Inspecting the plack error logs, I saw The given date (02/26/986) does not match the date format (us) at /usr/share/koha/lib/Koha/DateUtils.pm line 168. To replicate: Edit a patron. Set the first digit in the year of the patron's birthday to 0, e.g for a 'MM/DD/YYYY' formatted date, this would be '02/26/0986' Click save. This causes an Internal Server Error. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 22796] New: koha-common and mariadb start in the wrong order
by bugzilla-daemon＠bugs.koha-community.org 23 Sep '23

23 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22796 Bug ID: 22796 Summary: koha-common and mariadb start in the wrong order Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P5 - low Component: Packaging Assignee: koha-bugs(a)lists.koha-community.org Reporter: shifting-koha(a)shifting.ca QA Contact: testopia(a)bugs.koha-community.org CC: mirko(a)abunchofthings.net Target Milestone: --- when running my last apt-upgrade, koha-common and mariadb both updated. Unfortunately, koha tried to configure before mariadb did, meaning that the database server was still stopped when koha tried to run it's configuration: Setting up linux-image-amd64 (4.9+80+deb9u7) ... Setting up koha-common (18.11.04-1) ... Upgrading database schema for library DBI connect('database=koha_theatrealberta;host=localhost;port=3306','koha_theatrealberta',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2 "No such file or directory") at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1517. DBIx::Class::Storage::DBI::catch {...} (): DBI Connection failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2 "No such file or directory") at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1520. at /usr/share/koha/lib/Koha/Database.pm line 107 dpkg: error processing package koha-common (--configure): subprocess installed post-installation script returned error exit status 255 Setting up mariadb-server-10.1 (10.1.38-0+deb9u1) ... of course, this was easy to fix by running "dpkg-configure -a" again. But it would be nice if these packages configured themselves in the right order. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5