Ticket #2531308 (closed defect)
ReporterAndrew Niema |
Opened: 10/15/11 Last modified: 04/17/12 Status: closed Type: defect Resolution: fixed |
Owner Thomas S. Sha |
Target Release: 3.5.0 Priority: P3 (normal) |
|---|---|---|---|
| Summary: | File Upload is not working | ||
| Description: | When trying to upload a file using IO module FireBug lists an error: Tested on FF 7.0.1 and IE 9 both for Windows. |
||
| Type: | defect | Observed in Version: | 3.4.1 |
| Component: | IO | Severity: | S3 (normal) |
| Assigned To: | Thomas S. Sha | Target Release: | 3.5.0 |
| Location: | Library Code | Priority: | P3 (normal) |
| Tags: | Relates To: | ||
| Browsers: | IE 9.x,Other | ||
| URL: | |||
| Test Information: | Using below example I excpected to see alert box either "succ" of "fail". No alert is popping at all. Test case:
|
||
Change History
|
Posted: 10/17/11
|
|
Posted: 10/18/11
Hi, No, with "sync:false" that error remains the same. |
|
Posted: 10/18/11
I have a working app on 3.3.0, which uploads files, and it stopped working on 3.4. |
|
Posted: 10/18/11
Please see http://yuilibrary.com/projects/yui3/ticket/2530999 and confirm the report is applicable for 3.4.1 and not 3.4.0; I cannot reproduce the error when testing against 3.4.1. If you are able to reproduce this error in 3.4.1, please provide a complete and functional example that demonstrates this condition. The test case you provided is not a functional example. |
|
Posted: 10/18/11
ok, my problem was it was "sync:true", and I didn't see any note in user guide, that this is not allowed. The test case I provided is using "success" and "failure" events which are not fired in file upload using iframe (I forgot that), and they caused that error no matter sync was true of false. Please update the user guide so other people won't fall in the same hole and maybe save some time. |
|
Posted: 10/18/11
BTW - in 3.3.0 i am using sync:false, and correct events, AND it still throws this error when changed to 3.4.1. |
|
Posted: 10/18/11
|
|
Posted: 10/18/11
Please have a look at the section on uploading files using IO: http://yuilibrary.com/yui/docs/io/#uploading-files-in-an-html-form Here, it specifically states that for file uploads, the event cycle is: Start, Complete, End. Feel free to reopen this ticket when you have additional reproduction data. |
|
Posted: 10/25/11
I am getting this same error when using TIMEOUT and io-upload-iframe Test case:
|
|
Posted: 10/25/11
Also, I get the error even if I don't specify any event callbacks. |
|
Posted: 10/25/11
The test case does not show how the upload is actually being triggered. (The test case you provided is nearly a duplicate of the original submission.) Additionally, the success and failure events are not fired for file uploads. Per my comment on 18, October, the event cycle is: start, complete, end. It would be easier if you can direct me to a production example that demonstrates the reported issue. |
|
Posted: 10/30/11
ok, let's get back to my case (sorry Jack) :) Thomas, please take a look at this example:
Now, when it's run, the complete event does fire, alert is popping up, but the "l.c.abort is not a function" comes up too. This error breaks further code execution. |
|
Posted: 10/30/11
I can confirm what Jack Chan said - then TIMEOUT is removed, this error stops occuring. |
|
Posted: 10/31/11
Thank you. I can confirmed the reported behaviour. |
|
Posted: 11/1/11
The startTimeout and clearTimeout functions between io-base and io-upload-iframe are colliding; the io-upload-iframe module is using the wrong functions. |
|
Posted: 11/1/11
|
|
Posted: 11/1/11
The startTimeout and clearTimeout functions between io-base and io-upload-iframe are colliding; the io-upload-iframe module is using the wrong functions. |
|
Posted: 11/1/11
|
|
Posted: 11/8/11
Ticket #2531370 was marked as a duplicate of this ticket. |
|
Posted: 03/29/12
Ticket #2532068 was marked as a duplicate of this ticket. |
|
Posted: 04/17/12
Closing out bugs checked in to 3.5.0. |
Jenny Donnelly
Synchronous mode is not supported when uploading files. I suspect this configuration is triggering the error.