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

[Bug 19898] New: Koha 17.11 - Upload Local Cover Image Failed - " Cannot process file as an image"
by bugzilla-daemon＠bugs.koha-community.org 29 Mar '18

29 Mar '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19898 Bug ID: 19898 Summary: Koha 17.11 - Upload Local Cover Image Failed - "Cannot process file as an image" Change sponsored?: --- Product: Koha Version: 17.11 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbutosi(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl In Koha 17.11, I am trying to upload a .jpg image to a bibliographic record (as a local cover image). After uploading, then clicking "Process Images", I get the following error: "Cannot process file as an image. Cannot process file as an image. Please ensure you only upload GIF, JPEG, PNG, or XPM images." I've tried to upload the file as a .jpg, .png, and .gif. The error persists. I've also tried to upload a different .jpg file. The error still persists. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[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 10679] Lists interface offers delete option when user doesn't have permission
by bugzilla-daemon＠bugs.koha-community.org 29 Mar '18

29 Mar '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10679 Marjorie Barry-Vila <marjorie.barry-vila(a)collecto.ca> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marjorie.barry-vila@collect | |o.ca -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 13976] Sorting search results by popularity is alphabetical
by bugzilla-daemon＠bugs.koha-community.org 29 Mar '18

29 Mar '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13976 BASE Library Consortium <baselibrary.consortium(a)nhs.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |baselibrary.consortium@nhs. | |net --- Comment #4 from BASE Library Consortium <baselibrary.consortium(a)nhs.net> --- Still relevant - Koha 16.05 and 17.11.03 search for a title and apply sort filter Popularity (most to least) - results are sorted by biblionumber ASC -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 20331] New: Patrons search results sorting and pagination does not work properly
by bugzilla-daemon＠bugs.koha-community.org 29 Mar '18

29 Mar '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20331 Bug ID: 20331 Summary: Patrons search results sorting and pagination does not work properly Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: josef.moravec(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Try this: Go to patrons module Search for patrons Try to paginate - you can do it once, second click does not work Try to sort - you can sort once on column, second click on same column heading does not work. Sorting on Expired on does not work. Caused by commit 744e9a03791f50be98cb5c43cb4223f31fa30ed4 Bug 20145: Do not insert 0000-00-00 in patron tests (and more) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 11317] Add a way to access files from the intranet
by bugzilla-daemon＠bugs.koha-community.org 28 Mar '18

28 Mar '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11317 --- Comment #132 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- The use case for us would be to allow access to files generated on the server - not logs, but print notices. They contain patron information, so you need to secure them behind login. -- You are receiving this mail because: You are watching all bug changes.

1 0

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

28 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

[Bug 11317] Add a way to access files from the intranet
by bugzilla-daemon＠bugs.koha-community.org 28 Mar '18

28 Mar '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11317 Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |rel_18_05_candidate Status|Passed QA |Failed QA --- Comment #131 from Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> --- 1. Not unicode proof, create a file named "❤" in your accessdir and boom: Can't call method "mtime" on an undefined value at /home/vagrant/kohaclone/tools/access_files.pl line 61. 2. Please rename accessdir with access_dir 3. Can we get an up-to-date and complete test plan? 4. Why do not we have a default value for accessdir? 5. What is the main purpose of this development? How do we want to advert it? Still log files? 6. Did someone test with very big files (see bug 8437)? Should we put a limit? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15115] Editing item information on active course reserves should not be allowed.
by bugzilla-daemon＠bugs.koha-community.org 28 Mar '18

28 Mar '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15115 --- Comment #1 from Jessie Zairo <jzairo(a)bywatersolutions.com> --- This is still an active issue. Some libraries face massive updates to reserves when switching terms to update items in course reserves module. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 20145] New: borrowers.datexpiry eq '0000-00-00' means expired?
by bugzilla-daemon＠bugs.koha-community.org 28 Mar '18

28 Mar '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20145 Bug ID: 20145 Summary: borrowers.datexpiry eq '0000-00-00' means expired? Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org See bug http://lists.koha-community.org/pipermail/koha-devel/2018-February/044322.h… Koha::Patron->is_expired returns 0 if $self->dateexpiry eq '0000-00-00' And there is a test I wrote for it on bug 17578 (commit 5a0a2ce584dec74808f471b0f92b2114c3d6029e , GetMemberDetails - Remove is_expired) But then we also have, in C4::Circulation::CanBookBeIssued: 752 if ( !defined $patron->dateexpiry || $patron->dateexpiry eq '0000-00-00') { 753 $issuingimpossible{EXPIRED} = 1; 754 } else { With a test: is( $issuingimpossible->{EXPIRED}, 1, 'The patron should be considered as expired if dateexpiry is 0000-00-00' ); So, my questions, do you have a very old Koha installations to search if there is borrowers.is_expired == "0000-00-00" in it? Do you remember if it meant expired or not at some point? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14