> 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.
Oke ;)
> 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 ?
Hmm, i'll have to investigate that, but i am rather busy atm.
> 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.
What flash version are you using? Did you try to upgrade it to the
latest version?
> 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 absolute did NOT want the plugin to be dependent on jQuery.ui, so if
you can rewrite it so it doesn't use any other jQuery stuff i would be
happy to give you the credits for it and include the fix in the code.
> 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.
Working on that also.
