(1 replies, posted in General discussion)

the problem is that plupload doesn't parse JSON. You should parse the json when the upload completes and then program accordingly to the message returned.

http://www.plupload.com/punbb/viewtopic … 6339#p6339

when you said not responding, I'm interpreting that the code execution isn't reaching there. so, maybe there's an error on JSON.parse(), try to run this code on firefox with firebug and verify if the firebug console is showing any error.

it's a setting, so you should put in the initialization


(4 replies, posted in Core API)

if you know how to use firebug I will suggest you to change the runtime to HTML5 so you can see if the url is being called through the NET tab in firebug, but remember the uploader should be in the top window, not inside a frame or iframe, or else firebug won't show the request.

About the "&". I don't think the "&" is the problem that the URL is not being called, but change it to & and see what happens.

the value is being sent. I'm using firebug to track the request and the name parameter is there.

this is what shown in the firebug at the POST tab:

 Content-Disposition: form-data; name="name"



(4 replies, posted in Core API)

to me your code looks correct, are you sure that the up.start() are being called? Maybe some error is ocurring before this call.

please post an working example in jsfiddle like:


so we can take a look.

when using the queue widget, don't use the bind method to the events, you should put the event code in the initialization like the statechanged event code:



(1 replies, posted in General discussion)

AFAIK, the isp only changes the ip when the user reconnect. but if you're using chunked upload, you wont have problems when the ISP changes your ip between requests


(1 replies, posted in General discussion)

use the stop method


http://www.plupload.com/plupload/docs/a … oader.html

wrong url:


changed the state check place and I think it's all ok now:


you should verify if the plupload is starting the upload:

if (up.state == plupload.STARTED && !validateForm()) {



(2 replies, posted in General discussion)

you should assign the failed status to the file:


adapted your code to jsfiddle:


And it's working fine here.

maybe what you need is to define the state changed event inside the initialization code as I did.

you should use the multiple_queues option:



(1 replies, posted in Core API)

with HTML4 you can't access the file through javascript code, so, chunking is not possible.

but if you want progress bar when sending files with html 4 traditional way, take a look on this:


try this:

var uploadInitialized = false;
uploader.bind('StateChanged', function() {
    if (!uploadInitialized) {
        if (!<form validation>)
        } else {
            uploadInitialized = true;
    } else {
        if (uploader.files.length === (uploader.total.uploaded + uploader.total.failed)) {

you should use the StateChanged event. Take a look on the events example:



(7 replies, posted in General discussion)

If you are the developer, I have a suggestion:

Plupload allows you to specify multiples runtimes for an uploader, so, if the client doesn't support the first runtime it will try the second, and so on.

so I suggest you to allow the user to select the order of the runtimes for the uploader.



(1 replies, posted in General discussion)

if in the front end it's showing 100%, probably the problem is at your server side code. Verify if you have permission or enough free space to write big files at your server

did you tried returning false on your error function?

there is no "max_file_count" setting. read this topic:



(1 replies, posted in General discussion)

please post you entire code, preferably in www.jsfiddle.net, like:



(2 replies, posted in Core API)

try to put the events inside the initialization code, see this sample:


the problem with what you want is that your user will have to upload the file two times, one to your server and another to the S3 bucket, I think your users won't be happy with this.

I have two solutions in mind:

- creating threads in php, so the user will not have to wait for the upload to s3 buckets. (I'm a ASP NET programmer, so I can't help you with this)

- uploads first to the s3 bucket, and after the upload, your server will download the file from the bucket to gather the information.