Hey SixTease, thanks for responding. Couldn't find those variables in the .cgi script but found it in the same html render page in the form of:
<form name="mnu1" action=$cgiurl method=POST style="margin-top: 0">
<input type=hidden name=user value="$user">
<input type=hidden name=pass value="$pass">
<input type=hidden id=a name=a value=soap>
During my research while trying to solve this I came across jQuery a few times and its structure looked quite different, so it seemed a lot of work to change. The site is an application form for my agency, so there are a lot of links on many of the pages, linking to the Payment form, where they put in how they want to be paid, different application forms, then to submit translation samples and so on, so I'd like to spare myself a lot of work. But I have noticed its all a bit slow in general, and was told this is because Perl hooked up to the .dbf dbase is a lot slower than php and mysql (which I know a lot more). Been getting about 30 applicants a day, so not a great load, and seems to work well enough when I occasionally get big projects and need hundreds of people to submit their translation samples.
Submit buttons in forms work in all the browsers, so it's just this link thing.
Seemed to work before on my previous server, but then I ran into problems and the programmer said he had to change something at the top of the cgi file, I believe:
$|=1;
print "Content-type: text/html\n";
print "Pragma: no-cache\n\n\n";
BEGIN {
$ENV{DBI_PUREPERL} = 2; # or =1
unshift @INC, "$ENV{'DOCUMENT_ROOT'}/cgi-bin";
}
use strict;
use CGI qw(:standard);
use DBI;
Somewhere in there. Could it be because of the new server? Switched to that because they can support sqlite, and generally a better service in many ways. Thanks for all your help. Karel
