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

[Bug 16976] New: Authorities searches with double quotes gives ZOOM error 20003
by bugzilla-daemon＠bugs.koha-community.org 17 Apr '18

17 Apr '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16976 Bug ID: 16976 Summary: Authorities searches with double quotes gives ZOOM error 20003 Change sponsored?: --- Product: Koha Version: 16.05 Hardware: PC OS: Linux Status: NEW Severity: critical Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: miguel.tuimil(a)xercode.es QA Contact: testopia(a)bugs.koha-community.org Any search on authorities(authorities/authorities-home.pl) that includes double quotes, for example "Enrico Fermi" gives: Software error: ZOOM error 20003 "can't set prefix query" (addinfo: "@or @attr 7=1 @attr 1=Heading 0 @attr 1=Heading-Main @attr 5=1 @attr 4=6 "\\"Enrico Fermi\\""") from diag-set 'ZOOM' -- You are receiving this mail because: You are watching all bug changes.

1 45

[Bug 17816] New: Useless call to GetBibioData in bulkmarcimport.pl(?)
by bugzilla-daemon＠bugs.koha-community.org 12 Apr '18

12 Apr '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17816 Bug ID: 17816 Summary: Useless call to GetBibioData in bulkmarcimport.pl(?) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: gmcharlt(a)gmail.com Reporter: glasklas(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz This call to GetBibioData seems without purpose: https://github.com/Koha-Community/Koha/blob/2fe2ef41bd8bf2f142597e39f493edb… $biblioitemnumber is either overwritten on the lines below, or update/create failed/was skipped and the later AddItemBatchFromMarc will fail anyways. -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 16072] New: Include only one small spinner gif in the staff client
by bugzilla-daemon＠bugs.koha-community.org 11 Apr '18

11 Apr '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16072 Bug ID: 16072 Summary: Include only one small spinner gif in the staff client Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW 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 Right now we have two spinner gifs for use when a "loading" icon is needed: spinner-small.gif loading-small.gif We only need one. The latter is used more often, but the former is transparent and thus probably more versatile and should be kept. -- You are receiving this mail because: You are watching all bug changes.

1 13

[Bug 18724] New: Upload cover image failed without error message
by bugzilla-daemon＠bugs.koha-community.org 08 Apr '18

08 Apr '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18724 Bug ID: 18724 Summary: Upload cover image failed without error message Change sponsored?: --- Product: Koha Version: 16.11 Hardware: All OS: Linux Status: NEW Severity: minor Priority: P5 - low Component: Tools Assignee: gmcharlt(a)gmail.com Reporter: sebastian.krieg(a)tuz-eisenach.de QA Contact: testopia(a)bugs.koha-community.org Created attachment 63948 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=63948&action=ed… koha-error.log: error messages with description of related steps to upload cover image Uploading a cover image failed without an error in UI, error message "no cover image available" is shown in the catalogue entries. There are error messages in koha-error.log but this messages are shown for every step (see the described steps in attachment): - open the administration site - go to "tools|catalogue|upload cover images" - upload a cover image This error a duplicate with every try uploading a cover image. -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 19451] New: Let borrowers-force-messaging-defaults.pl optionally add preferences only when not already present
by bugzilla-daemon＠bugs.koha-community.org 06 Apr '18

06 Apr '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19451 Bug ID: 19451 Summary: Let borrowers-force-messaging-defaults.pl optionally add preferences only when not already present Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz A welcome addition to borrowers-force-messaging-defaults.pl would be to allow adding the messaging defaults only to patrons without such preferences. This will be made possible with the empty_only option. It copies the prefs only when the borrower prefs are empty (read: are not present). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 25

[Bug 19527] New: Alter Zebra indexing to sort by descending document ID
by bugzilla-daemon＠bugs.koha-community.org 01 Apr '18

01 Apr '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19527 Bug ID: 19527 Summary: Alter Zebra indexing to sort by descending document ID Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Zebra Assignee: koha-bugs(a)lists.koha-community.org Reporter: r.delahunty(a)arts.ac.uk We are receiving complaints about the sorting order of relevance ranked searches. One specific example was where the older edition of a work appears higher up the list than the more recent version. According to http://www.indexdata.com/zebra/doc/administration-ranking.html: “If one defines the staticrank:1 directive in the main core Zebra configuration file, the internal document keys used for ordering are augmented by a preceding integer, which contains the static rank of a given document, and the index lists are ordered first by ascending static rank, then by *** ascending *** document ID.” Would it not be better to have the secondary rank in terms of ** descending *** document ID? That way there is much better likelihood that the most recently published version of various editions will appear closer to the top of the OPAC list, and certainly (all else being equal) above the earlier edition(s) of the specific work. Ray Delahunty University of the Arts London -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 18815] New: OpenLibrarySearch is broken
by bugzilla-daemon＠bugs.koha-community.org 31 Mar '18

31 Mar '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18815 Bug ID: 18815 Summary: OpenLibrarySearch is broken Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org When turning on OpenLibrarySearch the label OpenLibrarySearch will show last in all search result entries, but nothing will display after it. The web dev tools show an error: XML Parsing Error: not well-formed Location: https://openlibrary.org/search.json?q=de Line Number 1, Column 1: -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 19147] New: Error when create new patron
by bugzilla-daemon＠bugs.koha-community.org 30 Mar '18

30 Mar '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19147 Bug ID: 19147 Summary: Error when create new patron Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Database Assignee: koha-bugs(a)lists.koha-community.org Reporter: j.jeyakumar(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Software error: Template process failed: undef error - DBIx::Class::Storage::DBI::_dbh_execute(): Expression #1 of SELECT list is not in GROUP BY clause and contains nonaggregated column 'koha_jeya.me.id' which is not functionally dependent on columns in GROUP BY clause; this is incompatible with sql_mode=only_full_group_by at /usr/share/koha/lib/Koha/Objects.pm line 120 For help, please send mail to the webmaster ([no address given]), giving this error message and the time and date of the error. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 18228] New: Working title
by bugzilla-daemon＠bugs.koha-community.org 29 Mar '18

29 Mar '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18228 Bug ID: 18228 Summary: Working title 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: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl -- You are receiving this mail because: You are watching all bug changes.

1 63

[Bug 17941] New: CanBookBeRenewed is very inefficient/slow
by bugzilla-daemon＠bugs.koha-community.org 29 Mar '18

29 Mar '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17941 Bug ID: 17941 Summary: CanBookBeRenewed is very inefficient/slow 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: boutrosboutrosboutros(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com I started investigating why populating the checkout list in the patron view sometimes took ages (minutes), and on occations even causing the system to almost halt because of DB overload. It turned out that reason is calls to C4::Circulation::CanBookBeRenewed. The critical factor is whether an item has many holds on it, and if there are many items that can fill the hold. Briefly looking at the code it seems obvious that the time spent grows exponentially with the number of holds and items. As one example, checking if an item with 111 holds (and 12 items on the biblio) can be renewed takes around 25 sec and generates over 18,000 SQL queries. I can't help to think there must be some missed "early returns" opportunities in the loops somewhere. For example, if there are more unfulfilled holds than available items, can the item ever be renewed? If no, return before even begin to calculate.. However, I know holds are full of complexities and things I probably haven't thought about so I need to dig into the code more. I would be very gratefull if anyone knowledgeable about this part of the code could help me find some ways to optimize this! -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 54