HTML FORM

Anon

This is my form:

</FORM>

I want to send the "message" from this form to "message.php" without going to "message.php". In other words, I just want to send the information from the form to "message.php" and then the from will clear itself so I can send the next message. It's like chatting kind of form. If anyone know how please let me know.

thanks in advance,

Chris

amcgrath

Put the form in message.php and send it to itself (form target...? is that new or something?)

Anon

I have two files.

One called: message.html
the other called: message.php

The form is in "message.html", sending info to "message.php"... I want the form to send the info to "message.php" without actually going there. I want the page to just stay in "message.html".

Thanks,

Chris

fenikso

Chris, don't you mean action="message.php"? I guess target is for hrefs.

And Allen's suggestion is quite right, AFAIK. It would keep you on the same page, and you could display contents based on your require method, GET or POST.

amcgrath

Send and go are pretty much the same thing in this case. Again, I reiterate, combine message.html and message.php into one script. The user submits the form data onto itself, message.php processes the data, and redisplays the same form.

vsego

If you insist on two files (though I agree with Allen and Rod - put the form in message.php), you can do this:

message.php:
<?php
...process your data WITH NO OUTPUT TO BROWSER
header("Location: message.html");
?>

That's it. Nothing may be outside <?php ?> block!

And in message.html, use:
<form action="message.php">...

target="..." is used with frames.

Anon

I am sorry... yes I meant action="message.php"

and even with action it didn't work...

Chris

Anon

Thank you guys... I will try and let you guys know, what's up...

Chris

amcgrath

Chris, I deliberately didn't mentionthis too (and hoped no one would) simply because think aobut it: a post to message.php is one request, and the redirection is another. it's a little thing, but little things add up.

vsego

Exactly. That's why I said I still prefer your put-it-all-in-one-script approach. But, if Chris insists, that's his problem.