CAPTCHA Anti-Robot Mod

Are you using a template that makes use of the MegaMenu. I am not a coder and I cannot find the thread where I thought I read that the ContactUs functionality within the MegaMenu uses different code than the stock ContactUs code and may not have the Spam protection embedded within that portion of the code.

We started receiving Spam from our Sandbox site after installing a template using Megamenu. Prior to that, we never received any Spam.

Maybe a coder can either confirm or dispute these observations.

DivaVocals:

It's a "deterrent" which means it will help prevent most normal spam.. but it's not bullet-proof and neither is CAPTCHA..

Exactly.. So like you pointed out SOME of the spam battle has to be manage using your e-mail client/host..

Well, I have both all my host's systems activated as well prior to even asking this question.

I am indeed using the Abbington Mega Template where the Mega Menus are used.

RixStix:

Are you using a template that makes use of the MegaMenu. I am not a coder and I cannot find the thread where I thought I read that the ContactUs functionality within the MegaMenu uses different code than the stock ContactUs code and may not have the Spam protection embedded within that portion of the code.

We started receiving Spam from our Sandbox site after installing a template using Megamenu. Prior to that, we never received any Spam.

Maybe a coder can either confirm or dispute these observations.

and THAT is the issue.. The contact form in the mega menu does not use the built in spam deterrents that are a part of Zen Cart's default Contact Us page.. It is my understanding that Anne opted not to use the CSS spam deterrent code for the contact_us form in the mega menu because it didn't validate..

HTML validation not a FINAL answer because the validator does still choke on code that is NOT invalid.. Adding the code CSS SPam deterrent code back to the mega menu contact us form will solve the issue.. I can't remember which support thread I saw this on, but it's posted on the forum somewhere..

Validate the code: Is it always necessary to pass the validation?

Assuming that for a developer being able to validate the code he’s creating usually represents a personal satisfaction as well as a challenge with himself, is it always necessary to pass the validation?

The green check mark that indicates a validated code is generated by a software in accordance with the result provided by an algorithm developed to verify the correctness of the code under exam. Considering that a software has some very strict rules, it can happen that the code of a Web document, even if perfectly developed, for whatever kind of banality not foreseen by the validation algorithm, may not be validated

and one more..

Acceptable Validation Errors

Ideally all your pages would be 100% valid, though it’s not practical or even desirable at times to achieve 100% validation.

Some code that’s commonly used just won’t validate. Vender specific prefixes such as -webkit and -moz will never validate by definition. That doesn’t mean you shouldn’t use those vendor specific prefixes.
Hacks for specific browsers (I’m looking at you Internet Explorer) also won’t validate, though it’s unlikely you’ll find a developer who’s never written a coding hack. Sometimes they’re all you have to get the page working right.
Validators will also issues warnings in addition to errors. 100% valid code means 0 errors, but it could include any number of warnings. Some of those warnings aren’t going to be things you’ll want to fix. Many tracking parameters you add to the end of a url will give a warning for example.
In the end you shouldn’t sweat it if your pages aren’t 100% valid. Some errors and many warnings are perfectly acceptable as part of a well-coded page.

and I couldn't resist one more.. Source: http://net.tutsplus.com/articles/general/but-it-doesnt-validate/

GOOD article on the real value of validation..

Validation is Not…

• A game. Don’t waste time achieving a 100% score, when you know exactly what you’re doing. However, do use it to point out your mistakes.

• An all-encompassing checker. While it does test for errors, it does not point out bad practices, accessibility issues, etc.

• To be used as an excuse for not embracing the latest CSS3 techniques. The longer you say to yourself, “I’ll use this in a few years…” the further you’ll fall behind.

and here is the answer to the CSS spam code not being included in the mega menu:

http://www.zen-cart.com/showthread.php?202327-Sheffield-Blue-Template-Support-Thread&p=1199787#post1199787

The file that needs changing is /YOURSHOP/includes/templates/responsive_sheffield_blue/common/tpl_mega_menu.php

Design75:

Add this line ```php

> after```php
<br class="clearBoth" />
                        <label for="enquiry">Message<span class="required"> *</span></label>
                        <textarea name="enquiry" cols="40" rows="3"  id="enquiry"></textarea>

and YES, this code will cause the template to fail w3c xhtml validation. This the reason why it was not included in the mega menu code. but to quote Design75:

Design75:

Ahh the autocomplete error :) That is one of those error I ignore completely, like the ones thrown at us about id's facebook uses

For those of you OBSESSED with that 100% validation score, you can use an encoding tool to encode this code which will shut the validators up.. (and for those getting ready to ask, you will need to Google encoding or start a separate thread to discuss further..)

I could care less about Validation! :) I need to get my old copy of my local store setup to verify this before I make any live changes.

THANKS!!
Chris

g2ktcf:

I could care less about Validation! :) I need to get my old copy of my local store setup to verify this before I make any live changes.

THANKS!!
Chris
Well validation IS important.. it's just not the holy grail that many believe it is..

Good luck..

Well, changes made and its made little if any difference. The comment about folks being paid to "contact us" appears to be valid. I was tempted to filter the IPs but I am sure that I would end up getting some good emails with that approach as well.

So...I will keep using the delete button :(

so since 1.5+ ahs its own spam detterent this mod is really not needed anymore?

Cause I installed it and then went to admin, set the layourt setting as instructed then clicked the link for captcha and the page comes up empty

[Attachment no longer available]

Will this work on Testimonial Manager?

DarkAngel:

so since 1.5+ ahs its own spam detterent this mod is really not needed anymore?

Cause I installed it and then went to admin, set the layourt setting as instructed then clicked the link for captcha and the page comes up empty

[Attachment no longer available]

as has been said several times, v1.5.x has a built in spam deterrent. So NO this module is no longer needed..

gsallen101289:

Will this work on Testimonial Manager?

the best spam deterrent is to not allow testimonials from non registered visitors..

DivaVocals:

the best spam deterrent is to not allow testimonials from non registered visitors..

I agree. Although some customers will not leave one to avoid the hassle of registering or may just not want to register. Maybe I just need to migrate to 1.5.

Mwaaaaa haaaaaa haaaaa yay! one less mod to install...LOL
ty

Of late I am getting spammed across all of my v1.5 sites via the contact us form. How can I eliminate this?

I had the same result. I noticed that the sql file were missing quotes on a lot of table names and other places.

timbojrjr1:

I had that same problem you have to change you sql file as in the readme on the top of the sql. I had to go into phpAdmin > your database > Configuration_group and then you have to see what the next two numbers would be at the end of your group GID:34 Sort order: 34 something like that and then change that in your sql file you load. Otherwise it just seems to put that Captcha Validation in whatever file has that GID: and Sort Order: that you had in the sql file you uploaded. There can be more than one page for this Configuration_group folder also if you have a lot of add-ons. Hope this helps.

Configuration group only gives gID not sort order. So where do find the right sort order?

This mod was poorly explained in readme. No mention is made of appending dbase prefix like zen_ or whatever. Missing quotes in sql file make installing database tables difficult.

Does this need to be turned on in 1.5.1 or is it on by default. I've been getting spam from my contact us page the last couple of weeks. I'm not sure if it's someone manually doing it or a robot/crawler.

Thanks

Shortly after upgrading to 1.5.3 I am not getting a tonne of contact form spam. I had captcha working on my old 1.3.9h system, but it seems that the magical new default spam blocking in 1.5.3 is not working for me. I'm on the cusp of installing this module to block it, but thought I would check if anyone else is having the same issue.