Problem with Script

**SUtrap** · Apr 11 '07, 10:25 AM

Re: Problem with Script

Hi,

I've done something similar some time ago, but my structure was a bit
different (I wanted to be very flexible):
1. I used an array to have all questions saved, like:
$question[x]="Question X"; Also all other values (your radio
values) were saved as arrays!
That way you dont have to look at the whole page to change some
text! My page was in english, german and french, so I had three files
each for one language.
2. I've used functions to generate the questions, like
getQuestion($nu mber), which returned the whole question + html string
for the buttons.

3. I've never used empty() call, only isset(); As far as I know it
wont write any warning about unset variables. dont know if empty()
does the same.
4. Dont save $Variable1=$_PO ST['Variable1']; ! As long as you dont
manipulate the data you dont need this!

5. Most of your html code is the same only the values change. you
could use such code:

.....html stuff...
<?php for($i=0;$i<siz eof($questions) ;$i++) { ?>
---- your question x, as function or embedded php ----
<?php } ?>
.....html stuff.....

6. Maybe you can also separate the html stuff completely from PHP,
with SMARTY or other template.

I hope that gives you some hints ;)

**Jerim79** · Apr 11 '07, 08:45 PM

Re: Problem with Script

For the moment, the biggest question before me, is how to make it so
that the user doesn't have to recheck each line if the form fails to
verify. Here is an idea. What if upon submission, I were to exclude
any questions from the form that were already answered correctly? Such
that the first time through, it prints out all questions. Upon
submission it verifies each variable. If all the variables contain
data, then we move on to the next page. If a variable contains no
data, then we repost the question to the user. Within the "IF
($error>0)" I could wrap each occurrence of a question with an IF
statement to see if data for that variable has already been entered.
If not, then it prints the question. If so, it skips on to the next
IF.

You say not to use $Variable1=$_PO ST['Variable1']. But after
correcting the problem questions, how would I pass along the value for
the correct questions as well? Usually I use hidden buttons on the
form to send along values. Let's say I have three radio groups, A, B
and C. User picks an answer for A and C but skipped B. When the form
validates, and reprints question B, how would I include the value of A
and C so that when the user clicks submit for the second time, the
previous values are not over written? Does isset() maintain its status
throughout all submissions? (As far as I know, PHP can only hold one
form at a time. If you submit another form, then the values of that
form overwrite the previous form.)

**ELINTPimp** · Apr 13 '07, 09:15 PM

Re: Problem with Script

On Apr 11, 3:38 pm, "Jerim79" <m...@hotmail.c omwrote:

For the moment, the biggest question before me, is how to make it so
that the user doesn't have to recheck each line if the form fails to
verify. Here is an idea. What if upon submission, I were to exclude
any questions from the form that were already answered correctly? Such
that the first time through, it prints out all questions. Upon
submission it verifies each variable. If all the variables contain
data, then we move on to the next page. If a variable contains no
data, then we repost the question to the user. Within the "IF
($error>0)" I could wrap each occurrence of a question with an IF
statement to see if data for that variable has already been entered.
If not, then it prints the question. If so, it skips on to the next
IF.

Does isset() maintain its status
throughout all submissions? (As far as I know, PHP can only hold one
form at a time. If you submit another form, then the values of that
form overwrite the previous form.)

You're correct about having to retain the state of those variables
that were answered "correctly" . You can do this like you initially
suggested, passing it back and forth from server to client each time
using $_POST or $_GET using hidden values in the form or using a
cookie on the client...but another way to do it, to save network
resources and the like, is to save it on the server. If you're using
a database, I suggest using transactions. You can "store" the
variables in the transaction until the user get's them all "correct"
and then commit the transaction. That would also give you the added
benefit of using rollbacks if the transaction fails at a later part.
Another way is to use sessions and to save those variables deemed
"correct" as a session variable. That way, the only thing that you
would need to send back and forth from the server to client would be
the session ID.

Problem with Script

Problem with Script

Comment

Comment

Comment