Re: CGI and forms (GET vs Post)

2000-01-06 Thread Eric L. Brine
> I read on w3 that they suggest 'post' for when there are no > visible changes, and 'get' when there are (or perhaps the other way > around). This seems a bit confusing. What is the difference in > laymen's terms? Other way around. GET is to be used when there is no side effect. e.g. when

Re: CGI and forms

2000-01-06 Thread Etienne Pelaprat
Hi Darren, i've put in the force parameter as you suggested, and things seem to be working a lot better. I think the problem may now lie in the method of the form. I read on w3 that they suggest 'post' for when there are no visible changes, and 'get' when there are (or perhaps the other way aro

Re: CGI and forms

2000-01-06 Thread darren chamberlain
Hi Etienne, CGI forms are "sticky"--they remember their value from the previous call, even if you manually set a value. Try adding a -force=>1 to the hashref that gets passed into the submit function ($q->submit(-name=>'submit',-value=>'Modify',-force=>1), for instance), which should tell CGI.pm

CGI and forms

2000-01-06 Thread Etienne Pelaprat
Hi, I'm having trouble with a script is use for posting, modifying, and submiting queued news to a database that gets used by another script to (to display stuff in the database). When no parameters are passed in, the script displays a list of all the articles waiting to be posted (from a databas