User Verification (Anti-Robot / CAPTCHA)

[tvadpro]

Can the people who reported trouble with the eval() problem above try the attached .sql file (again, cut-and-paste, don't upload it) and let me know if it's any better?

Success 9 statements processed.
Error ERROR: Cannot insert configuration_key "ACCOUNT_VALIDATION" because it already exists
Error ERROR: Cannot insert configuration_key "CREATE_ACCOUNT_VALIDATION" because it already exists
Error ERROR: Cannot insert configuration_key "LOGIN_VALIDATION" because it already exists
Error ERROR: Cannot insert configuration_key "ENTRY_VALIDATION_LENGTH" because it already exists
Error ERROR: Cannot insert configuration_key "ENTRY_VALIDATION_LENGTH" because it already exists
Warning Note: 4 statements ignored. See "upgrade_exceptions" table for additional details.

...
Tonight was my first encounter with the CAPTCHA contrib -- thanks for sharing this one! I installed, configured, then noticed the unexpected T_CONSTANT_ENCAPSED_STRING error message when trying to edit the length of the validation code. Just now found this thread when I searched the forum. Ran the additional SQL and now I have two instances of Configuration/CAPTCHA Validation. Looks like I need to revert to the database backup I did just before pasting & running the first SQL, then have a closer look at the statements before I try processing them again.

Once this is fixed, my next mission will be to find a way to include CAPTCHA on the tell-a-friend email form. I don't want to require visitors to create an account just so they can use tell-a-friend, but I don't want to leave the door open for a malicious bot either.

One thing at a time, eh?

[tvadpro]

OK -- I did the database restore, then ran the revised SQL and I'm pleased to report it worked great for me. I can edit the length of the validation code, which I set to 4.

HOWEVER, I am not able to create a user account. When I fill in all the required fields and the CAPTCHA code & press submit, it just reloads the form without creating a new customer account. There is no error message or alert/notice text.

Since this is a fresh install of 1.3.5, I dunno whether the failure is in any way related to my CAPTCHA installation. I guess I could try creating the user account with CAPTCHA disabled and see what happens ...

[tvadpro]

That was easy ... I set Activate Validation to FALSE, then attempted to create a customer account. This attempt succeeded, which suggests I have a problem with my CAPTCHA installation.

Any idea what might prevent validation of the form?

[funkey]

That was easy ... I set Activate Validation to FALSE, then attempted to create a customer account. This attempt succeeded, which suggests I have a problem with my CAPTCHA installation.

Any idea what might prevent validation of the form?

I'll look into this, but i've had a few e-mail reports of the CAPTCHA form Javascript not working.

If you disable Javascript in your browser, the code should use the standard MessageStack warning to alert you that the CAPTCHA details aren't completed.

[funkey]

Tonight was my first encounter with the CAPTCHA contrib -- thanks for sharing this one! I installed, configured, then noticed the unexpected T_CONSTANT_ENCAPSED_STRING error message when trying to edit the length of the validation code. Just now found this thread when I searched the forum. Ran the additional SQL and now I have two instances of Configuration/CAPTCHA Validation. Looks like I need to revert to the database backup I did just before pasting & running the first SQL, then have a closer look at the statements before I try processing them again.

Ah, I probably should have made that clearer -- Use the .sql file in Post 50 instead of the one in the download, not as well as.

I'm still waiting to hear from the other people who have e-mailed me as to if the new .sql code I posted actually fixes the problem, if it does -- i'll release an updated version to the download area.

Then work on porting everything cleanly to 1.3.6.

Cheers,

Paul

[tvadpro]

If you disable Javascript in your browser, the code should use the standard MessageStack warning to alert you that the CAPTCHA details aren't completed.

Yeah, I looked high and low, but no warning displayed anywhere -- it simply reloaded the page like I'd never been there before or somethin'.

And I'm pretty sure javascript is still enabled on my browser. There's the off-chance it's blocked by my McAfee, but Internet Security hasn't interfered with any other javascript components, at least not lately.

Think I'll sleep on it for the time being. Only thing I want to know in the next 24 hours is whether I should restore the database again to pre-CAPTCHA state, lest I need to do it down the road and wind up losing gobs of additions and changes.

[funkey]

Yeah, I looked high and low, but no warning displayed anywhere -- it simply reloaded the page like I'd never been there before or somethin'.

And I'm pretty sure javascript is still enabled on my browser. There's the off-chance it's blocked by my McAfee, but Internet Security hasn't interfered with any other javascript components, at least not lately.

Think I'll sleep on it for the time being. Only thing I want to know in the next 24 hours is whether I should restore the database again to pre-CAPTCHA state, lest I need to do it down the road and wind up losing gobs of additions and changes.

An easy way to tell, if you don't fill in another one of the required fields (say, the state), does:

* a javascript window pop up titled "Errors have occurred during the processing of your form."

-or-

* a red box at the top of the login page that says "Please select a state from the States pull down menu." with a warning icon next to it.

[tvadpro]

Initially I did a few like that, just to be sure the warnings worked. Left the validation code field empty too, and warnings displayed as expected. Wasn't until I filled everything in properly that it reloaded the registration form and omitted warnings altogether.

[funkey]

Initially I did a few like that, just to be sure the warnings worked. Left the validation code field empty too, and warnings displayed as expected. Wasn't until I filled everything in properly that it reloaded the registration form and omitted warnings altogether.

OK.

Out of interest, if you pick a U.S state from the dropdown box -- does it still do the reload?

Just wondering if you're actually triggering one of the state selection bugs that were in 1.3.5, I actually disabled the drop-down box in my test install, which seems to have fixed that particular issue.

Which is actually fixed 1.3.6, out of interest.

[tvadpro]

Just wondering if you're actually triggering one of the state selection bugs that were in 1.3.5, I actually disabled the drop-down box in my test install, which seems to have fixed that particular issue.

The customer registration form on my 1.3.5 has no drop-down ... at least not at first. Initially it just has an INPUT field (see source below). So if I type in a known 2-letter state abbreviation, e.g. PA or FL, I get a warning and a form with both a state SELECT/OPTION (dropdown) and state INPUT field. (This happens regardless of whether CAPTCHA is active.) I can submit the form successfully on the first try only if CAPTCHA is inactive and I spell the full state name, e.g. Pennsylvania or Florida.

Source code from first create-account form on 1.3.5:

<label class="inputLabel" for="state">State/Province:</label>
<input name="state" size="33" maxlength="32" id="state" type="text">&nbsp;<span class="alert">*</span><input name="zone_id" type="hidden"><br class="clearBoth">

I'm leaning toward upgrading to 1.3.6, so this might all become moot for me in a day or two. I'm running 1.3.6 on at least one other site, and so far it's mostly trouble-free.