posting variables from forms

[windandwaves]

With a form, I have two buttons.

One of them says:
- pay here

The other says
- pay somewhere else

Now, can I change the location to which the variables from the Form are
posted, depending on the button that they click? or am I always restricted
to the location specified in the action (e.g. <form method="post"
action="mynewpage.php">)

TIA

- Nicolaas

[Ian Collins]

windandwaves wrote:

With a form, I have two buttons.

One of them says:
- pay here

The other says
- pay somewhere else

Now, can I change the location to which the variables from the Form are
posted, depending on the button that they click? or am I always restricted
to the location specified in the action (e.g. <form method="post"
action="mynewpage.php">)

Not without a little bit of JavaScript on the page to implement an
onclick handler for the button.

--
Ian Collins.

[Geoff Berrow]

Message-ID: <11***************@drone2-svc-skyt.qsi.net.nz> from Ian
Collins contained the following:

Now, can I change the location to which the variables from the Form are
posted, depending on the button that they click? or am I always restricted
to the location specified in the action (e.g. <form method="post"
action="mynewpage.php">)

Not without a little bit of JavaScript on the page to implement an
onclick handler for the button.

Yuck!

Why not put both methods in mynewpage.php and choose which one to use
depending on which button is pressed?

--
Geoff Berrow (put thecat out to email)
It's only Usenet, no one dies.
My opinions, not the committee's, mine.
Simple RFDs http://www.ckdog.co.uk/rfdmaker/

[Al]

> Why not put both methods in mynewpage.php and choose which one to use

depending on which button is pressed?

Somewhere else might be a different site.

Having said that, if "somewhere else" can take GETs rather than POSTs,
you can direct all form traffic to one php file and see which submit
button name/value pair is activated and then either run the script if
it's "here" or do a header("Location: ") if it's the "somewhere else"
one... But that IS a little odd, and the javascript method is a little
smoother.

[windandwaves]

Al wrote:

Why not put both methods in mynewpage.php and choose which one to use
depending on which button is pressed?

Somewhere else might be a different site.

Having said that, if "somewhere else" can take GETs rather than POSTs,
you can direct all form traffic to one php file and see which submit
button name/value pair is activated and then either run the script if
it's "here" or do a header("Location: ") if it's the "somewhere else"
one... But that IS a little odd, and the javascript method is a little
smoother.

Yes, it is funny. Because it seems to make sense that depending on the
choices from the user the data may have to go to site A or site B. Doing
the header function means that you loose the posted variables as posts so
that you have to post them again. Can you do something like this:
header(post-type, $_POST), basically directly reposting all posted variables
to a new location?

HTMS (hope that makes sense)

- Nicolaas

[Al]

windandwaves wrote:

Doing
the header function means that you loose the posted variables as posts so
that you have to post them again. Can you do something like this:
header(post-type, $_POST), basically directly reposting all posted variables
to a new location?

Well yes, it loses the informaiton as POSTs but you can recreate them
as GETs and send them on their way in a header("Location: ");

But if you want to resend as POSTs I think it's mildly impossible. I'm
pretty sure you can't do it your way. The header() command just adds
stuff the to header being sent back to the user, rather than the header
of the redirected request, unfortunately :)

I think the javascript way seems to be your only chance, and it's not
particularly invasive. Plus if people have javascript disabled then you
can default to my POST -> GET code and at least TRY to fulfil the silly
non-javascript-user's request :)

So yeah, employ both methods?

[Pedro Graca]

windandwaves wrote:

Can you do something like this:
header(post-type, $_POST), basically directly reposting all posted variables
to a new location?

Have a look at cURL <http://www.php.net/curl>.

--
If you're posting through Google read <http://cfaj.freeshell.org/google>

[Jim Michaels]

some people don't have JavaScript - some Accessible machines for the
disabled, for instance.
I found this out when reading a book on making sites accessible.

"Al" <al************@gmail.com> wrote in message
news:11**********************@g44g2000cwa.googlegr oups.com...

windandwaves wrote:

Doing
the header function means that you loose the posted variables as posts so
that you have to post them again. Can you do something like this:
header(post-type, $_POST), basically directly reposting all posted
variables
to a new location?

Well yes, it loses the informaiton as POSTs but you can recreate them
as GETs and send them on their way in a header("Location: ");

But if you want to resend as POSTs I think it's mildly impossible. I'm
pretty sure you can't do it your way. The header() command just adds
stuff the to header being sent back to the user, rather than the header
of the redirected request, unfortunately :)

I think the javascript way seems to be your only chance, and it's not
particularly invasive. Plus if people have javascript disabled then you
can default to my POST -> GET code and at least TRY to fulfil the silly
non-javascript-user's request :)

So yeah, employ both methods?

[Al]

Jim Michaels wrote:

some people don't have JavaScript - some Accessible machines for the
disabled, for instance.

Well yes, my smiley was to show I was only joking. But if you saw, I
did say that both methods should be employed and that the default
behaviour should be the nicer-working JavaScript one.