[RESOLVED] Multi-part Forms

akitaz

I know this has doubtless been asked before, though I've looked and can't find it...

I have a long form that needs to be split into five different pieces. What I'm trying to do is when the user hits the Submit button, it will validate data, ask for missing fields, etc. I have that largely figured out. Then when they hit the "next" button that will bring up the next part of the form and pass the captured data along, and so forth, until they finish the last piece, where all the data will be stuffed into an email. Later, into a mySQL database, but that's down the road. A "back" button would be nice, but not 100% critical.😕

Any help appreciated. TIA

Scriptmaker

Every time you move to a new page, you can "hide" the data from the last form in hidden fields in the current form.

page2.php:

<form action="page3.php" method="post">
<!-- get data from first form page -->
<input type="hidden" name="firstname" value="<?php echo $_POST['firstname'];?>">
<!-- end get data from first form page -->
<input type="text" name="lastname">
<input type="submit">
</form>

page3.php:

<form action="page4.php" method="post">
<!-- get data from first form page -->
<input type="hidden" name="firstname" value="<?php echo $_POST['firstname'];?>">
<!-- end get data from first form page -->

<!-- get data from second form page -->
<input type="hidden" name="lastname" value="<?php echo $_POST['lastname'];?>">
<!-- end get data from second form page -->

<input type="text" name="age">
<input type="submit">
</form>

Rodney_H_

I don't suggest hidden form elements.

I do suggest using SESSIONS to store the data until it is all needed OR you can store the data in a mySQL table setup to hold TEMP data, and pull it all and delete it when things are completed per requirements.

You can then run a CRON job to delete all items that are older than a day or two, so the TEMP table won't fill up with unfinished form submissions.

BUt, the easiest thing would be to use SESSIONS.

Scriptmaker

yep, forgot to mention that I said "hide" because the data isn't truly hidden and therefore not really private.

If you want to see an example of Rodney's suggestion:
http://blog.taprootcreative.com/?p=24

akitaz

I appreciate the suggestions. I'll give them a try and see how it goes.

akitaz

OK, what I was missing was the use of the header(Location: <some URL>); to tell it where to go next. In looking at the sample code on taproot, and digging through the book I'm using, the light finally went on. I did wind up using SESSION variables to pass things on from page to page.

Thanks again for your help.