Radio Button Help

need_help_php

Here's what i'm trying to do: i have a page, with a form, where a user selects a templete via radio button, click ok, and then is sent to the next page, where they make another choice, and so on. The values are all in radio buttons, so what i'm trying to do is that the value would be passed on to the next page, etc. So that when the user is on the very last page, they can see all the choices they have made. Here is what i have so far:

 $temp1 = 'unchecked';
$temp2 = 'unchecked';
$temp3 = 'unchecked';

if (isset($_POST['Submit'])) {

$tempid = $_POST['tempid'];

	if ($tempid == 'temp1') {
		$temp1 = 'checked';

	}
	elseif ($tempid == 'temp2') {
		$temp2 = 'checked';
	}
	else($tempid == 'temp3') {
		$temp3 = 'checked';
	}
}

and then the HTML section is here:

<h1>Choose your templete and click OK </h1>

<form id="templetes" name="templetes" method="post" action="">


<!-- Templete 1--><label>
  <input name="temp1" type="radio" value="radio"  />
<img src="templetes/templete1.jpg" alt="templete1" width="195" height="234" border="0" /></label>
<br /><br />

<!--Templete 2 --><label>
  <input name="temp2" type="radio" value="radio"  />
<img src="templetes/templete2.jpg" alt="templete2" width="183" height="228" border="0" /> </label>
<br /><br />

<!--Templete 3 --><label>
  <input type="radio" name="temp3" value="radio"  />
  <img src="templetes/templete3.jpg" alt="templete3" width="174" height="230" border="0" /></label>
<br /><br />
<input type="submit" name="Submit" value="OK" />
</form>

I have a feeling that the code is not all correct, so please let me know.
Now i need to pass the value to the next page, but it cannot be visible yet. it has to be in the url, and then another value whould be added, and both will be passed on through to the third page. ex: templetechoice.php is the first page. depending on the templete they choose, the url on the next page could be choosebackground.php?tempid=1 , and the next one would be choosemusic.php?tempid=1&backround=2, etc.
Can someone please help me with doing that?
thanks in advance.

h4x0rmx

I usually read the passed value and then "store it" in a hidden field

<INPUT TYPE=HIDDEN NAME="tempid1" value="true">

but since you will be passing the same data different times it's probably not a good idea, anyway is not very secure at all... (maybe you could use an array)

You could use Sessions, I personally believe that sessions should only be used for sensitive data (passwords, etc), but they can make your life easier specially on what you're trying to do now.

http://www.google.com/search?hl=en&client=firefox-a&rls=org.mozilla%3Aen-US%3Aofficial&hs=Zpa&q=php+session&btnG=Search

Can anyone come up with a better solution? :p

bpat1434

Sessions would be the easiest thing. Just start a session at the first form, then when it's submitted take the submitted values and put them in the $SESSION array. Continue this process until the last page where you can then read from the $SESSION array to see what the posted values were.

Note that using hidden fields will allow the user to change the value at any point in time during the form process. So you might be weary of doing that.

Another option is to use one huge form, but set each of your smaller "forms" into a form fieldset and using javascript, define which fieldset is visible, and when they click "next" hide the currently visible fieldset, and unhide the next. This allows you to submit only one form while making it look like they're using smaller forms.

h4xormx, you can use sessions for anything. It really shouldn't be for sensitive data (like passwords) since sessions can be sniffed and hijacked. This is a perfect example of when to use sessions. Use during logins and to verify their authenticity. But storing passwords in a session is usually a bad idea (even if it's just a hash).

h4x0rmx

bpat1434;10881653 wrote:
h4xormx, you can use sessions for anything. It really shouldn't be for sensitive data (like passwords) since sessions can be sniffed and hijacked. This is a perfect example of when to use sessions. Use during logins and to verify their authenticity. But storing passwords in a session is usually a bad idea (even if it's just a hash).

My bad, I didn't mean to say that it's a good practice to store passwords on sessions, I just use them to authenticate users.
I though there was a limit on the size of the sessions, but I'm probably wrong. What say ye, bpat1434?

bpat1434

Sessions are only limited to the space of the session save type. If it's saved in files, it's limited by disk-size, otherwise, whatever storage mechanism is its limit. Usually they're stored in text-files in something like /usr/php/session or /tmp/session or something like that.

I still don't keep their passwords in the session. Usually for authentication I keep a security token that is a hash of something unique to them in the session, store that in the DB and do a quick verification to see if they're the same. Not very secure, but I'm not worried about session hijacking too much. I'm not working on any huge projects (yet) 🙂

h4x0rmx

Thanks bpat1434, let's see what your need_help_php friend says.