(2 replies, posted in General discussion)

This might help:


I'm pretty sure the basics of how a resized image's dimensions are determined has not changed in a very long time.  It sill works the same in 1.3.

But I don't know what a Yii extension is so I can't help you there?




(1 replies, posted in General discussion)

Just the jquery widgets require jquery.  The core API is entirely self contained and can be used without including jquery (or any other library for that matter) to select and upload files.  You will have to build the interface of course.

You could try reading these two posts, they might help.




(8 replies, posted in General discussion)

Can you share some code?  What you are talking about sounds like an unusual implementation.

There is a sticky post on this topic (It's sitting at the top of the list of posts in the forum with more or less the same title as your post).  Here is the direct link:



(8 replies, posted in General discussion)

Not sure if you are talking about exactly the same thing, but perhaps this thread from earlier today would be helpful:


This topic gets discussed a fair bit on the forum.  This thread may also be helpful:


AFAIK you can return anything you want from the server.  Then write your own code in JavaScript to look at the returned data and do whatever you want with it. 

It is in your hands, plupload does nothing other than passing the response from the server back via a callback you register against the FileUploaded event.

You need to provide more details if someone is to help you.  What happens when you load your web-site in a browser?  Are there any messages in the console? etc.

I haven't reviewed your code in details but ast @davit mentioned you must call the init function after you bind the Init event, but before you bind any of the other event handlers.  See below:

        uploader.bind('Init', function (up, params) {
            $('#filelist').html("<div>Current runtime: " + params.runtime + "</div>");

        uploader.init   // ** Call init here.

        $('#uploadfiles').click(function (e) {


(3 replies, posted in General discussion)

You can examine the source code for the examples to see how they are put together - that is the intended use for the examples.

An installation how to was written recently as well, it may be of help:



(3 replies, posted in General discussion)

Start by looking at the examples that come with plupload.


(1 replies, posted in General discussion)

This post from a couple of days ago may be helpful:



(6 replies, posted in General discussion)

The examples are just that, examples of how to make use of plupload, its API and plugins.  You are under no requirement to use a particular file or directory structure for your own use of plupload.  Also, depending on what components of plupload you choose to use, all of the files are not needed.

I think @davit's advice was to simply get the examples up and working.

I'm a little confused.  What request are you referring to?

Plupload will upload a file to the server.  There is already sample php code to handle the server side processing in the examples bundled with plupload.  Have you looked at and tried out the examples?


(6 replies, posted in General discussion)

Which example are you trying to run?

I don't think there are any AJAX calls to the server before you upload the files in any of the examples.  I know the custom example certainly loads fine without needing to make any AJAX calls.

Before you purchase a license you should test plupload to make sure it meets your needs.

1 - You specify the runtimes as a list ordered from best choice to worst.  For example I use "html5,flash,html4".  plupload will then try to us html5 if the browser supports it, then flash if html5 is not available, and finally html4 is the final fallback which all browsers support.  But html4 has limitiations like no multiple file selection which many users want which is why it is last in my list.

2 - You should look at the examples that come with plupload.  There is some php code for server side which should give you an idea of how to handle server side processing.

3 - Since you have the source code for plupload you can add anything in theory - not sure how easy it is to add bitrate as I only use the core API and not the widgets.

Again I'd recommend trying plupload out in a test application before deciding if it meets your needs.


I'd suggest you start by simply trying what @davit has suggested above.  If it works you problem is solved.  If it doesn't then you can start worrying about why at that point in time.

There is no formal API for this.  As @davit mentioned a few posts ago you need to sort the uploader.files javascript array before you call the uploader.start method to begin the actual upload of the selected files.  The plupload code uploads each file as a seperate POST - but you can pick the order of those POSTs by sorting the uploader.files array.

If you read the thread you might note that it is not titled properly.  The issue was in fact with the Server Side php and file system configuration.  Linux didn't have anything to do with the problem.

It's responding the way it is currently designed to work.  Stopping upload will not halt a file that has already started its upload - it just stops subsequent uploads from starting.

I believe this has been added to both html5 and flash runtimes in the 1.4.3 release.