Bug 9955 - Partly broken local cover image uploading
Summary: Partly broken local cover image uploading
Status: CLOSED INVALID
Alias: None
Product: Koha
Classification: Unclassified
Component: Tools (show other bugs)
Version: 3.10
Hardware: All All
: P5 - low normal (vote)
Assignee: Galen Charlton
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-29 15:25 UTC by Serhij Dubyk
Modified: 2014-12-07 20:02 UTC (History)
2 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Serhij Dubyk 2013-03-29 15:25:17 UTC
Unable to connect local cover images. Loading hangs at 100% and then not possible to process the image.
Suddenly it occurs in Firefox browser in Linux (Debian testing) and in Windows (XP).  

In error console of Firefox appears this error:

Eror: TypeError: jQuery.handleError is not a function
Source: http://koha.tntu.edu.ua:8888/intranet-tmpl/prog/en/lib/jquery/plugins/ajaxfileupload.js
Line: 111

The browser Chromium has no such problem.

Found here (http://stackoverflow.com/questions/13107536/jquery-handler-error-is-not-a-function) that the jQuery.handleError was removed after the jQuery version in 1.5 and need to write a custom error handler function.
Comment 1 Liz Rea 2013-03-29 22:16:44 UTC
Out of curiosity, can you attach an image you are trying to upload that does this? I haven't been able to replicate your issue.

Liz
Comment 2 Liz Rea 2013-03-29 22:18:10 UTC
Also, what version of Koha are you experiencing this with?
Comment 3 Serhij Dubyk 2013-04-01 12:10:07 UTC
Example of cover: http://library.tntu.edu.ua/wp-content/uploads/2011/01/978-5-222-16446-4.jpg

Firefox Iceweasel 19.0.2 - freeze at 100% uploading.
but with Chromium 25 all ok - http://koha.tntu.edu.ua/cgi-bin/koha/opac-detail.pl?biblionumber=17454

Koha 3.10.03.000, Debian 7.0 testing.
Comment 5 Owen Leonard 2014-04-24 14:07:27 UTC
This report is over a year old now and I've not heard any confirmation for this problem, nor can I reproduce it. I'm guessing it was a local configuration issue, but if the problem persists and is reproducible please re-open the report with new details.