[RESOLVED] Proper way to make somebody accept terms

jasonyoung

I'm very annoyed. It seems like I'm stuck in a mental loop. What I'm attempting seems so simple, but it's proving to be difficult.

All I want are users to complete a form, agree to the terms by clicking a checkbox and then submit the form.

I've got javascript validating the sceniario, but after reading other threads I guess I shouldn't rely on client-side technology in case its diabled.

I tried a php script, but it requires them to post the form before I can validate it. If it fails validation, one of two things happen.

If I echo the error, the database gets updated anyway AND the form redisplays.
If I collect the errors in an array and dump them to the screen, the form redisplays, with the errors listed at the top, but now all of the entries they initially entered are wiped out!. WTF?

ANY SUGGESTIONS ANYBODY?

MrPotatoes

process.php

[code=php]
    if ($accept_terms == 'yes')
    {
        $_SESSION['proceed'] = true;

        #do code
    }
    else
    {
        $_SESSION['proceed'] = false;
        echo 'no douche, you gotta click onthe terms';
        exit();
    }

[/code]

process.php
[code=php]
    if ($accept_terms == 'yes')
        (bool)$checked = true;
    else
        (bool)$checked = false;

    if (!$checked)
    {
        echo 'sorry dude, you HAVE TO ACCEPT the terms to go further';
        echo "<BR><a href=javascript:history.back()>BACK</a>";
    }

[/code]

i prefer the second way.

Roger_Ramjet

So when you redisplay the form, add the data that they did fill out as values to the input elements

echo '<input type="text" name="box1" value="' . $_POST['box1'] . '" />';

If you want to be slick you can do it like this for both the original display and the redisplay

$box1='';
$box2='';
$box3 = '';
$err = array();

if (isset($_POST['submit'])) {
   if (isset($_POST['box1'])) { 
      $box1 = $_POST['box1'] 
   } else {
      $err[] = 'box1';
   }
  if (isset($_POST['box2'])) { 
      $box2 = $_POST['box2'] 
   } else {
      $err[] = 'box2';
   }
  if (isset($_POST['box3'])) { 
      $box3 = $_POST['box3'] 
   } else {
      $err[] = 'box3';
   }

if (count($err) > 0) {
   echo implode($err , ',') . ' are required fields, please complete them and resubmit';
}
}

// now the form code once only

echo '<input type="text" name="box1" value="' . $box1 . '" /><br />';
echo '<input type="text" name="box2" value="' . $box2 . '" /><br />';
echo '<input type="text" name="box3" value="' . $box3 . '" /><br />';

I'll leave it to you do the rest.

MrPotatoes

yeah definatly add that. nothing worse than having to redo even the shortest of forms

Weedpacket

But still do all that in Javascript anyway; it makes for faster interaction. That's right. Do both: once for their benefit and once for yours.

jasonyoung

OK, I'm with you on doing both things, but what happens in this scenario?

I have a submit button which is disabled unless the agree box is selected. Javascript does this. If javascript is disabled, how would they submit? Do I need to do some javascript checking first to see if their browser will support the script?

I think I'm making this harder than need be.

Roger_Ramjet

WE had just that thing with an externaly developed and hosted website - not my idea but a 'business deal'. They were all into ASP. and the notion that nothing but IE mattered. So the asp/js validation would not work on anything but IE6. His excuse "but IE has 90% of the browser market". BOLLOCKS!.

The currrent solution from MickeySoft for all the virus vectors that IE introduces - and it is on MSN - is to DISABLE JAVASCRIPT IN IE?????????

Fat lot of good anything dependent on js to function will be when home users catch on to that.

JS is only any good to enhance the user's experience - save then from having to wait for a page reload before they get an error message. It MUST not be used for anything that is mission-critical. You certainly cannot stop a user from proceeding just because they failed any js validation. Things like relying on js to enable a submit button are STUPID - unless you want to loose business. All submit buttons must ALWAYS be enabled.

To check for js is OK; you can do that quite easily and enhance the user's experience accordingly. But you must code for the lowest common denominator - which in this case is JS=OFF.

FINALLY: here in the UK, and across the rest of Europe, the law states that services must be available to anyone. That means that any public website must be useable by anyone with a physical disability, so you need alts for all images for the vision-impared: and you need 'alts' for anyone accessing your website from an alternative user agent. That means someone using their tv, or mobile, or whatever. Such devices will not work with javascript validation, so you are breaking the law in europe if your website requires js to function.

see this articel or this article for more information.

THINK ABOUT IT.

OK, so no-one has been prosecuted - as yet - but someone will be one day.

jasonyoung

OK. So don't disable the Submit button or be stupid. Oops, too late, I'm stupid! Thanks. I'll change the code. But even so, the same problem remains. I think I should have mentioned something important in the initial post...

I'm allowing users to return to the same form and modify their fields again and again. This is required because usually people add modules during the sales process which requires us to have them visit the form and append those new values. As a courtesy, I'm echoing the existing MySQL values in the form. This way the existing DB entries are not erased when resubmitting the form. The code looks like this:

<?php
	if ($checkcp==1)
		{
			echo "
				<input name=\"ipcp\" type=\"text\" onkeypress=\"return handleEnter(this, event)\"  id=\"ipcp\" tabindex=\"200\" size=\"13\" value=\"$ipcp\"></td> ";
		}
	else
		{
			echo "
				<input name=\"ipcp\" disabled=\"true\" type=\"text\" onkeypress=\"return handleEnter(this, event)\"  id=\"ipcp\" tabindex=\"200\" size=\"13\"></td>";
		}
?>

So if I'm already reading the existing values in the DB, how could I change to have it populate their POST data instead?

I'm really trying hard to understand this but I'm still learning something new everytime I change something. I guess it all comes in time.

Thanks for any feedback.

Roger_Ramjet

OK so you are selling stuff: so you need to be as slick as possible. So the answer we worked out back in '96 is still the answer.

You need to be as simple to use as possible.
You need to make taking their money as easy as possible.
You do not want to raise any unneccessary barriers.
You do not want to let them think twice.
You know that the technology is unreliable: it is up to you to deal with that problem, not the user.

FORGET ABOUT SESSIONS.

Use a permanent cookie to track them.

Do not expect or require them to register or login untill AFTER you have taken the money.

Store all information in the database so that they never have to re-enter any of it.

Allow them to edit that information whenever they wish.

TAKE THE MONEY AND WORRY ABOUT THE DATA AFTERWARDS.

Now, for example, I currently work for a firm that outsources overdue accounts for large corporations:we sell bad debts, and anyone can buy them.

So I do no validation of user input before pasing them on to our payment processor. Invalid email? Who cares. No account number? Their problem. If they are too dumb to input the ref we supply then it is their fault if it takes us a long time to credit the right account. No contact information? Well, we've got the money and can wait untill they contact us. We have no risk cos we have nothing to loose. Of course, our payment processor is going to validate the card information properly, that is what we pay them for.

Now, I doubt that you are in quite that situation. You want to provide great customer service, and you are at risk. But the main issue still applies: take the money and worry about the other stuff once you've got it.

So, use a permanent cookie to recognise them.
Store all input in the database linked via the cookie data. If they delete the cookie then tough luck, they will have to re-enter something, but make it minimal.
Now you can still service them from page to page even if they break off half way through, or drop their connection, which was more the issue back in the '90s.

It is not 'a courtesy' to remember their details, it is essential business common-sense. Remember, untill you have the money the customer is King.

Now, how do you repopulate the form data? Have a look at my post in this thread 3rd post down.