Re: Input button question

[THRAK]

Chances are if you feel you haven't provided enough info, then you probably haven't! Generally this means you don't understand your own explaination so obviously it will be even tougher for those who are not inside your mind. Just my take on that comment.
It sounds like you want to run your script and go directly to the HTML page at the same time. (?) You can't have two actions for a single event, but you could call the script and at the end do a redirect to the page. If you don't always want to redirect to that page you will have to determine that by data you pass. (e.g. detect value of some hidden field.) Somewhat of a stab in the dark, maybe this will help you.

-THRAK
www.polarlava.com

[dawnamarr]

Yes, that is exaclty what I want to do, and I do want to do it each time that button is pushed.

Think you could provide an example? The code in the first reply isn't working for me - it only prints those statements out to the .pl page.

[ChemBoy]

I'm still not quite clear on the sequence of events, but I'm going to put what I think is happening and then what I think you should do (this is what we call "error propagation" in my line of work...)

1. Point browser to FOO.html
2. submit form to BAR.pl
3. BAR.pl modifies FOO.html
4. Browser is redirected to FOO.html

Is that right? If so, then the first suggestion is more or less right (for the "less", see use CGI or die;). The key is that those statements must be the first and only things printed to STDOUT by BAR.pl--if you print out a regular header first (using the header() method from CGI.pm), then it will just become part of the document body.

Since I've made a fair passel of assumptions so far, I'll go ahead and assume you're using CGI.pm, as well. In which case, replace your call to print header("text/html"); with one to print redirect($new_url); and all will be well.

I hope some of this is helpful--if my assumptions are totally off, we can go another round. :-)




---

If God had meant us to fly, he would *never* have give us the railroads.
    --Michael Flanders

[wardk]

If FOO.html is meant to be dynamic, then perhaps what you might want to do is put the FOO.html contents in BAR.pl and have BAR.pl print the FOO contents, which would change depending on the form field contents.

This way you don't have to maintain/edit the FOO.html file seperately (and updating the static page could get ugly... so if you do this contemplate using a perl templating module)

also, what if more than one person is using the site? Modifying FOO.html in a multi-user environment could be a flocking pain in the rear :-)

[THRAK]

I believe this is a reasonable interpretation, but the explaination and lack of any substantial code example has made this rather convoluted.

-THRAK
www.polarlava.com

[THRAK]

You would be better off posting what you have and what it is you are trying to accomplish. You can do a redirect using something like:
print $cgi->redirect($cgiurl);.
This is functionally equivalent to what suaveant has above.
You can learn more about the CGI module here.

-THRAK
www.polarlava.com

[suaveant]

Probably what is happening is you are printing out other headers above the redirect headers...

leave out the normal print "Content-Type: text/html\n\n"; or whatever you use and use mine... or if you are using CGI.pm, use the redirection routine that was pointed out below.
                - Ant