About the mysterious #2038 error xbill82 reported. I got it too. I asked several friends online to access my website and test it. The results were very mysterious. So:
On several computers we did not get the error.
Then on two computers that have WinXpSp2 and FF188.8.131.52 I got the error on only of them. It worked on both IEs on these PCs.
Then on two computers (one with Vista and another with XP2) we always got the error.
On one IE7 I got the error only some times, not always! I once got the error upon hitting the cancel button by the filename I wished to upload, that is, I got the error even when not specifically trying to upload the file! (I was amazed at that and yes, it's repeatable, see below).
I tried xbill82's solution of erasing the xajax_getFormValues() from the call to the uploader and it did not work. Another forum member mentioned that it was a <SELECT> tag inside a <TD> that was causing the problem. I am using no <select>s on this page, so it can't be it.
I eventually got to pin down the one factor that's leading to the error, although I believe this is not the real cause of the error, it's only an unlucky trigger: I have a <textarea> in my form. When I leave it blank or fill it with little text, it works ok. When I fill it with a lot of text, then I get the error on all the computers and browsers.
I then got back to the 2 pcs that were always giving the errors and left the textarea empty or with little text and lo and behold, NO Error! If I fill the text area with a lot of text, I always get the error even when hitting the cancel button (<div class="swf_queued_file_remove"/>)
I think we need to go deeper and investigate to be able to effectivelly correct this problem. This plugin is too damn useful! <select>s and <textarea>s and xajax_getFormValues() are legal to use and we need to use them in our forms. I don't think mysterious solutions are ok, because they either cripple our action or eventually let us down. I would like to help more, but at the moment I don't know how.