Gilles,
I have pursued my investigations.
I turned around the redirect issue by making sure that I return data
to the plugin and use the severData callback to invoke an ajax reload
of the div containing the uploaded picture.
The format for passing additional parameters is a simple object in the
form of { name: "value", name: "value"}.
When you use GET as method, the parameters are properlly added to the
query string and everything works just fine.
The crashing of Firefox 3.0.4 on Mac is due to passing the additional
form parameters in POST rather than GET.
In fact, passing additional parameters as POST does not work in any
browsers and platforms. The request is badly constructed. The parm
name is well passed as form-data name but the value is badly converted
to string and shows in the request body as [object Object]. Maybe an
issue in the AS constructing the request ?
Using GET, I managed to make the plugin work for me with a single
instance for a while than suddenly it stopped working again. I can't
figure out why. The log shows that the plugin initializes correctly,
handle all events properly up to and including fileUploadStarted. The
upload takes place, the backend script executes properly, the image is
loaded and updated in the DB, the backend script ends properly and
returns data to the browser. But the swf movie seems to be dead. It
does not trigger any event after fileUploadStarted : none of the
fileUploadProgress, fileUploadCompleted, fileUploadError,
fileUploadCancelled, queueCancelled, queueCompleted events.
I also found that the plugin does not behave right if you have
multiple instances of it on the same page. I have rewritten the js
part of the plugin to take advantage of jquery.ui.widget and I will
send it privately to you if you wish. It works now as I expected with
as many instances of the plugin as you like, each with its own
settings and callbacks. The only thing that woul be nice to have is
the extension of the logging facility to display the plugin instance
that triggers the events.
I am still stuck with the swf movie not triggering the events after
fileUploadStarted. Not being familiar with swf development, I don't
know if you have additional debugging facilities to identify what
would cause the swf movie not to trigger the events.
Let me know.
On 15 déc, 13:15, "Gilles (Webunity)" <gilles0...@gmail.com> wrote:
> I found this on another site:
>
> ----------------------------------------------------------------------------------------------------
> We use the FlashuploaderMultiPowUpload (http://www.element-it.com/
> MultiPowUpload.aspx) and Nirvanix HTTP upload. To register new uploads
> we use the forwardingurl to forward to a script on our site.
>
> Nirvanix makes a 303 redirect to the forwarding URL with only a header
> and no content. The problem is that Flash on Mac needs at least one
> char in the response content to accept it as a response and make the
> redirect - meaning upload on Mac is not working on our site.
>
> Can we in any way get just a single char in return when using the
> forwardingURL to fix this problem?
> -------------------------
>
> Maybe that helps with your issue
> 4?http://developer.nirvanix.com/forums/p/467/1634.aspx
