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

[Bug 9097] 'Welcome mail' for new library users
by bugzilla-daemon＠bugs.koha-community.org 04 Nov '19

04 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9097 Martin Renvoize <martin.renvoize(a)ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=23908 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 14759] Replacement for Text::Unaccent
by bugzilla-daemon＠bugs.koha-community.org 04 Nov '19

04 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14759 --- Comment #33 from Colin Campbell <colin.campbell(a)ptfs-europe.com> --- Looks like in addition to the problems of building on 64 bit systems it fails to build on the most recent versions of Perl. I think this is a result of the removal of . from the default path -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 7614] Use branch transfer limits for determining available opac holds pickup locations
by bugzilla-daemon＠bugs.koha-community.org 04 Nov '19

04 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7614 Martin Renvoize <martin.renvoize(a)ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|paul.poulain(a)biblibre.com |lari.taskula(a)hypernova.fi -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 23429] New: ilsdi.pl GetRecords documentation does not match output
by bugzilla-daemon＠bugs.koha-community.org 04 Nov '19

04 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23429 Bug ID: 23429 Summary: ilsdi.pl GetRecords documentation does not match output Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: J.P.Knight(a)lboro.ac.uk QA Contact: testopia(a)bugs.koha-community.org The ILS-DI GetRecords self generated documentation no longer matches up with the output that the script generates. It probably should. :-) For example, the documentation says that the <item> element contains a <date_due> element. This was the case back in 16.x versions of Koha, but on our production 18.11.04 we no longer get this field, but we do get an <onloan> field in item instead (which luckily serves the same purpose as we need - we just need to know if each item is on loan or not). Here's the example format for the <item> part of the record generated by http://ourserver/cgi-bin/koha/ilsdi.pl?service=Describe&verb=GetRecords <items> <item> <biblioitemnumber>1</biblioitemnumber> <withdrawn>0</withdrawn> <holdingbranchname>Bibliothèque Jean Prunier</holdingbranchname> <notforloan>0</notforloan> <replacementpricedate>2008-08-20</replacementpricedate> <itemnumber>1</itemnumber> <location>Secteur Adulte</location> <itemcallnumber>R ABE</itemcallnumber> <date_due></date_due> <itemlost>0</itemlost> <datelastseen>2008-08-20</datelastseen> <homebranch>BIB</homebranch> <homebranchname>Bibliothèque Jean Prunier</homebranchname> <biblionumber>1</biblionumber> <holdingbranch>BIB</holdingbranch> <timestamp>2008-08-20 17:15:51</timestamp> <damaged>0</damaged> <cn_sort>R_ABE</cn_sort> <dateaccessioned>2008-08-20</dateaccessioned> </item> </items> And here's what we get out for an actual search: <items> <item> <onloan>2019-10-01</onloan> <holdingbranch>MAINLIB</holdingbranch> <location>MAIN</location> <datelastborrowed>2019-07-18</datelastborrowed> <biblioitemnumber>526315</biblioitemnumber> <permanent_location>MAIN</permanent_location> <datelastseen>2019-07-18</datelastseen> <withdrawn>0</withdrawn> <itype>LONG</itype> <notforloan>0</notforloan> <biblionumber>526315</biblionumber> <itemnumber>847332</itemnumber> <price>22.17</price> <dateaccessioned>2016-09-13</dateaccessioned> <issues>10</issues> <homebranchname>Main Library</homebranchname> <homebranch>MAINLIB</homebranch> <timestamp>2019-07-18 17:03:03</timestamp> <cn_sort>005_550000000000000_SPS_BRA</cn_sort> <itemlost>0</itemlost> <renewals>28</renewals> <barcode>040444587X</barcode> <damaged>0</damaged> <replacementpricedate>2018-02-01</replacementpricedate> <itemcallnumber>005.55 SPS/BRA</itemcallnumber> <holdingbranchname>Main Library</holdingbranchname> </item> </items> Note the <date_due></date_due> in the example is missing from the real output, which has <onloan>...</onloan> instead. I guess we need to decide if the documentation is just out of date with the code, or if the code should be generating things it isn't any more. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 22128] New: koha-remove fails mysql ERROR 1133 (42000) at line 2: Can't find any matching row in the user table
by bugzilla-daemon＠bugs.koha-community.org 04 Nov '19

04 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22128 Bug ID: 22128 Summary: koha-remove fails mysql ERROR 1133 (42000) at line 2: Can't find any matching row in the user table Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: Heinrich.Hartl(a)email.de QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Target Milestone: --- The script fails in in a GRANT command - the user does not exist This probably is due to changed behaviour of mysql 5.7ff From https://dev.mysql.com/doc/refman/5.7/en/grant.html#grant-overview: Note If an account named in a GRANT statement does not already exist, GRANT may create it under the conditions described later in the discussion of the NO_AUTO_CREATE_USER SQL mode. It is also possible to use GRANT to specify nonprivilege account characteristics such as whether it uses secure connections and limits on access to server resources. However, use of GRANT to create accounts or define nonprivilege characteristics is deprecated as of MySQL 5.7.6. Instead, perform these tasks using CREATE USER or ALTER USER. In my case mysql hosted a koha 16.11 database upgraded to 18.5 and the only existing user was koha_library@%. There was no user koha_library@localhost. mysql was running in the version (> 5.7)supplied with ubuntu 16.4 (Xenial). My solution to the problem was commenting out two lines in the script. diff /usr/sbin/koha-remove /usr/sbin/koha-remove_ori 71c71 < # GRANT USAGE ON \`koha_$name\`.* TO \`koha_$name\`@\`$mysql_hostname\`; --- > GRANT USAGE ON \`koha_$name\`.* TO \`koha_$name\`@\`$mysql_hostname\`; 73c73 < # DROP USER \`koha_$name\`@\`$mysql_hostname\`; --- > DROP USER \`koha_$name\`@\`$mysql_hostname\`; hhl@koha-VM-dev:~ > For a general solution the koha-remove script should be made more resilient and should not use deprecated mysql features. Since I am only very occasionally dealing with mysql and moreover I have no knowledge which user(s) have been used for koha instances in the past it is beyond my skills to define the proper revision of the script. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 23

[Bug 15184] Ability to duplicate existing order lines to a given basket
by bugzilla-daemon＠bugs.koha-community.org 04 Nov '19

04 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15184 Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |23927 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23927 [Bug 23927] Duplicate a "Complete" order link the "New" one to the invoice -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 11514] Untranslatable "Uncertain" text in acq
by bugzilla-daemon＠bugs.koha-community.org 04 Nov '19

04 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11514 Owen Leonard <oleonard(a)myacpl.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #93323|0 |1 is obsolete| | -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 11514] Untranslatable "Uncertain" text in acq
by bugzilla-daemon＠bugs.koha-community.org 04 Nov '19

04 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11514 Owen Leonard <oleonard(a)myacpl.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|oleonard(a)myacpl.org |koha-bugs(a)lists.koha-commun | |ity.org -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 11514] Untranslatable "Uncertain" text in acq
by bugzilla-daemon＠bugs.koha-community.org 04 Nov '19

04 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11514 Owen Leonard <oleonard(a)myacpl.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEW -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 11514] Untranslatable "Uncertain" text in acq
by bugzilla-daemon＠bugs.koha-community.org 04 Nov '19

04 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11514 Owen Leonard <oleonard(a)myacpl.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Failed QA |ASSIGNED --- Comment #14 from Owen Leonard <oleonard(a)myacpl.org> --- (In reply to Jonathan Druart from comment #13) > Owen, you closed this bug but I think it is still useful. Even if it needs a > small adjustment. The bug refers to a translation issue and the translation issue is now invalid. If someone else want to continue to work on it I suggest at least renaming the report. -- You are receiving this mail because: You are watching all bug changes.

1 0