Well, that's why I moved
use GT::CGI;
before
use CGI qw/:standard/;
I theory that load order change is enough, as GT::CGI reads the STDIN first, so gets the POST input. And upload _works_ in most cases. There are just RARE cases, where I get that strange error. Unfortunately until that moment, I was not able to track down, what circumstances leads to the error. I was not even able to reproduce that upload error manually.
I used CGI mainly for upload tasks, but due to some compatibility problems, I had to move to GT::CGI usage. I preferred CGI over GT::CGI, as it provided more info methods about uploaded file.
I use GT::Session::File for session tasks, and only CGI::Cookie is related to the CGI module. I could move to GT::CGI cookie handling, that's just a matter of decision and some free time.
I don't remember at the moment (I'm now busy with my studies, and doing just bugfix on my online site), if there is any core CGI usage left in the code, but I think I can take out the CGI usage. Until the time I can check it in details, I will try to move the Links load before CGI load, hoping that this will solve compatibility problems.
BTW: do you know that array input results are reversed in the input read process?
This should be fixed, IMHO.
Best regards,
Webmaster33
Paid Support from Webmaster33. Expert in Perl programming & Gossamer Threads applications. (click here for prices)
Webmaster33's products (upd.2004.09.26) | Private message | Contact me | Was my post helpful? Donate my help...
use GT::CGI;
before
use CGI qw/:standard/;
I theory that load order change is enough, as GT::CGI reads the STDIN first, so gets the POST input. And upload _works_ in most cases. There are just RARE cases, where I get that strange error. Unfortunately until that moment, I was not able to track down, what circumstances leads to the error. I was not even able to reproduce that upload error manually.
I used CGI mainly for upload tasks, but due to some compatibility problems, I had to move to GT::CGI usage. I preferred CGI over GT::CGI, as it provided more info methods about uploaded file.
I use GT::Session::File for session tasks, and only CGI::Cookie is related to the CGI module. I could move to GT::CGI cookie handling, that's just a matter of decision and some free time.
I don't remember at the moment (I'm now busy with my studies, and doing just bugfix on my online site), if there is any core CGI usage left in the code, but I think I can take out the CGI usage. Until the time I can check it in details, I will try to move the Links load before CGI load, hoping that this will solve compatibility problems.
BTW: do you know that array input results are reversed in the input read process?
This should be fixed, IMHO.
Best regards,
Webmaster33
Paid Support from Webmaster33. Expert in Perl programming & Gossamer Threads applications. (click here for prices)
Webmaster33's products (upd.2004.09.26) | Private message | Contact me | Was my post helpful? Donate my help...
