I just found out that the error occurs, if I access my web application using a subdomain.
http://test.toplevel: works
http://sub.test.toplevel: Security Error

In my searches regarding this problem, I read some posts about an hidden iframe rendered by the HTML4 runtime.
Is there maybe some domain relaxing necessary?


Hello there,

when using HTML4 runtime, I get a "security error", despite the fact that the file was correctly uploaded.
HTML5 and Flash do work...

Do you have any hints on this?
I am using Plupload 1.5.x.


I just had a quick test with Plupload 2.x: same problem....
(but at the moment, Plupload 1.5.x is of relevant for me)


I have some more information:
I used Javascript console to trigger the click on the input element manually by

document.getElementById('<id of input>').click()

This works in Firefox and opens the file selector dialog, but in IE it doesn't. Also no exception is thrown on console.

In addition: All of this also doesn't work in Chrome, just as in IE (where is Chrome support is not important for me).

Please, help me. This is of great importance to me....

BTW: Currently I am using Plupload 1.5.x release.

Is this possible for HTML4 runtime?

- IE works with Flash
- HTML4 works with Firefox

=> HTML4 in IE doesn't work

Generated HTML markup seems good.
Have a look:


I am struggling with a mysterious problem.

I initialize Plupload with
browse_button = (i.e. id of link which is clicked)
container = (i.e. id of direct parent element)

This works in all browsers, except for IE (all versions) and HTML4 runtime.
Unfortunately, IE support and HTML4 is mandatory, since my customers use old IE9 and older without flash.

Can you please give me a hint on how to solve this?



at the moment I managed to implement kind of a workaround on this:
Since FileUploaded handler also gets a plupload file object passed

FileUploaded(uploader:Uploader, file:File, response:Object)

I am able to replace the wrongly decoded file name by

Obviously this only works for ANSI characters.
Other special characters not contained in the ANSI charset, like Chinese and Arabic will still fail though.

We are planning a release by the end of this week, so I'd greatly appreciate any estimation on this issue by your side.


It seems as if Plupload is unable to handle UTF-8 encoded server responses.

Could you please clarify that?
Are you able to fix this?

Hello there,

I am using Plupload 2 beta and I've got some encoding problems with the server-side response, which is received by FileUploaded event handler.

My test case is:
I upload a file called "äöÜÄÖÜ.txt".
In the response I receive, the file name is encoded "äöÜÄÖÜ.txt".

This happens only in IE.
I tried setting it to:
"text/plain; charset=UTF-8"
"application/json; charset=utf-8"
or setting no content-type at all.

All of these yield no difference.

Could you please help me?



(2 replies, posted in General discussion)

Small remark:
Unfortunately, since it was on their productive system, we couldn't take time have a look into the DOM structure or debug it.

Too bad that it didn't also occur on their development system.... :-/


(2 replies, posted in General discussion)


I have just another issue with the Flash shim.
We have shipped a version of our software to one of our customers, which contains Plupload 1.5.6.

They have a 3-level structure, which consists of a DEV system, a QS system and the productive system.
On DEV and QS our application with Plupload worked fine.
Yesterday our customer called me with a web session and showed me a behaviour on their productive system, where Plupload's Flash shim does not correctly merge with the correspondig ExtJS button, it is bound to, but in fact sits on top (!).

So he needed to click above the real button to hit the Flash object.

Any hints on this?

Kind regards,

> Just a thought, since you mentioned Ext JS
> is your page heavy lifted with
> other scripts and stuff?
> Maybe it is blocking loading of Flash in some way.

Yes, you are right, it is a rather big ExtJS application.

Do you have any hint on how ExtJS may interfere flash loading?
(Before moving to Plupload, we used the old swfupload (
This old one worked pretty fine, together with ExtJS.


No, I do not use these client side mechanisms.
Where can I get this smaller flash shim from?

At the moment I use "Moxie.swf", which is 33.740 KB large...


But since it's happening rather seldomly, I don't know how to reproduce it.
Next time I reload the page, flash will be initialized correctly.

But that's no option to ship our product....


I have configured Plupload's runtimes as follows:
In Firefox, HTML5 works absolutely fine, but in Internet Explorer I
sometimes experience a strange behaviour:
For some reason Pluplod does not render the flash shim, but instead an HTML4 shim.

Can you provide any help on this?

I don't want do have this happen within our shipped product...

Here are the two corresponding HTML-portions for comparison (I embedded Plupload into an ExtJS Button).


N.B. We are using a recent build of Plupload2.

Kind regards,


(12 replies, posted in Core API)

I've just included a small fix for this problem

function resolveFile(file) {
    var type = o.typeOf(file);
    if (file instanceof o.Blob) {
    } else if (type === 'file') {
    } else if (type === 'object' && file.getSource() && file.getSource().getSource()) {
     // this is the new case
    } else if (type === 'node' && o.typeOf(file.files) === 'filelist') {
    } else if (type === 'array') {

What do you think?


(12 replies, posted in Core API)

I've debugged a little bit, using the unminified code.
Method addFile() calls local function resolveFile(file). This determines the file's type by

function resolveFile(file) {
    var type = o.typeOf(file);
    if (file instanceof o.Blob) {
    } else if (type === 'file') {
    } else if (type === 'node' && o.typeOf(file.files) === 'filelist') {
    } else if (type === 'array') {

In my case,


returns "object", so this is not covered by one of the cases above.
What am I missing?


(12 replies, posted in Core API)

Dear Davit,

thanks to your latest improvements on Plupload2, I was able to replace Plupload 1.5.6 by current version of Plupload2.

So I am working on this approach.

I have set up two instances of Plupload: A main one and the second (arbitrary) one, from which I want to feed files added later on to the main plupload instance.

I am trying to do this in the QueueChanged handler:

var onQueueChanged = function(uploaderArbitrary){

Unfortunately no files are added to the mainUploader instance, which also means no QueueChanged or FilesAdded events for this instance get fired.

uploaderArbitrary.files seems to look well:

Is there maybe some configuration I am missing?



doesn't have an effet...

Thanks for your help,

Hello Davit,

great work, that fixed it!

Many thanks,


(112 replies, posted in News)

Could you please update plupload2 download link with newest compiled from github commits?

I am currently experiencing a strange behaviour with Plupload2 that might have been fixed just 4 days ago (



I have just replaced Plupload 1.5.6 by latest version of Plupload 2 (which is plupload_2_0a.24030126).

I have replaced the previous plupload.full.js by plupload.full.min.js and plupload.flash.swf by Moxie.swf.

But disregarding SWF, I mainly use HTML5.
When I try to upload more than one file, I get the following error:
> NOT_INIT_ERR: NOT_INIT_ERR: RuntimeError 1
The first file is uploaded correctly.
When trying to upload the second file, event "onUploadFile" is fired correctly, but after this, the upload process stops with the above error.

If I then click the file dialog button again, to try a new upload, I get the error message "TypeError: r is null".
I have to reload the whole page to start a new....

Firebug console:

I hope, you can provide some help...


(12 replies, posted in Core API)

I just took a look at your code on GitHub.
I found this method:

 * Adds file to the queue programmatically. Can be native file, instance of Plupload.File,
 * instance of mOxie.File, input[type="file"] element, or array of these. Fires FilesAdded, 
 * if any files were added to the queue. Otherwise nothing happens.
 * @method addFile
 * @param {Plupload.File|mOxie.File|File|Node|Array} file File or files to add to the queue.
addFile : function(file) {

If I understand correctly, I can instantiate an arbitrary drop zone with a second Plupload instance (e.g. plupload2) and then use



Thanks for the help,


(12 replies, posted in Core API)

Dear Davit,

how stable is 2.0 Beta?
Is it reliable?

Not to forget: is there an API documentation available, for the new 2.0 specific parts?


BTW, it seems as if your forum has been hacked....


(12 replies, posted in Core API)

Hi Davit,

In my case, I instantiate PLUpload upon loading the page. I.e. first loading the URL.
The button on which Plupload listens for clicks is directly visible, so can pass this DOM element to Plupload.

The drop target is created upon drag start. That means, I'd like to have an API in Plupload which allows me to bind the drop target later on, in time of drag start, when the drop area is created.

Do you consider this as possible?
We are about to integrate Plupload into our products and buy a licence, so your support is highly appreciated...