-
1. Re: Web Form Error
Matt Baracz Jul 31, 2013 6:42 PM (in response to inan-saligan)Hey inan-saligan,
I suspect this error has something to do with the 'Anti-bot Fraud Protection' module if you have it enabled for that form in particular. What I recommend you do is either of the following:
1. Re-insert the form onto your page and ensure you do not modify the field generated by the 'Anti-bot Fraud Protection' module.
2. Navigate to Site Manager > Web Forms > [select your form] and remove the 'Anti-bot Fraud Protection' module from this web form.
Cheers.
-
2. Re: Web Form Error
Liam Dilley Jul 31, 2013 10:01 PM (in response to Matt Baracz)Yeah, its got a bug tracking number (two actually I think for the different issues) - Basically does not work properly and randomly does this for some forms.
Matt, can you see if you can find out if it is on the cards to fix any time soon?
-
3. Re: Web Form Error
Matt Baracz Jul 31, 2013 11:41 PM (in response to Liam Dilley)Hey Liam,
I've just tested the form inserted on jdteterlaw.com and the error is no longer occurring. I believe this issue would have been occurring due to the customization done to that form because, as you know, that error message is returned when the hidden field generated by that module is populated. Regarding any bugs on this; there is a bug logged where we have requested to update the error message returned to something more generic (i.e. to remove the reference to the credit card). There has been progess made on this, however I don't have a firm date yet as to when this bug fix will be rolled out.
Cheers.
-
4. Re: Web Form Error
inan-saligan Jul 31, 2013 11:55 PM (in response to Matt Baracz)I fixed this already... I did the instructions that you gave me... I removed the anti-bot
Thanks!
-
5. Re: Web Form Error
Dave Blubaugh Aug 1, 2013 11:55 AM (in response to Matt Baracz)@Matt & @Liam
Hi Guys,
I agree with Liam. This is a form issue that needs to be addressed/solved.
If the 'Anti-bot Fraud Protection' module is for verifying credit cards then it should not automatically be on every form created. I have found that most forms created/used do not process credit cards (all forms on a non e-commerce site, contact forms, CTA forms, etc.), so why is it automatically included on each form?
I too found that removing the module fixed the issue. One interesting thing is that the form builder shows the 'Anti-bot Fraud Protection', but if I look at the source code it is displayed as {module_ccsecurity}.
Question:
Is it possible to edit {module_error}? On the error page the breadcrumbs have the site name in them. I don't want to show the site name because the company name and the site name are different. I use the site name to organize the dropdown box on the admin login page.
Cheers,
Dave
-
6. Re: Web Form Error
Matt Baracz Aug 1, 2013 6:11 PM (in response to Dave Blubaugh)Hi Dave Blubaugh,
To expand further on what I mentioned in my previous post; when a web form is created within the admin console, the 'Anti-bot Fraud Protection' module is now included by default. This module is not used to verify Credit Cards - what this module does is create a hidden input field (i.e. a honeypot) for that form. Therefore, if this hidden field is populated, an error will be returned. This is due to the fact that spam bots usually populate all fields as sometimes they cannot differentiate between whether a field is hidden or not - it is used as a preventive measure to reduce spam.
Now the confusion here is that the error returned is “ERROR: An error occurred while processing credit card”. This is because the feature was originally introduced for the online shop. As mentioned in my previous post, there is a bug logged where we have requested to update this error message to something more generic as this module is now used across all web forms. I suspect this update will be rolled out with our next release, however at the moment this is not something I can guarantee.
There have also been reports of this error being triggered randomly, yet this is not something we can replicate. Please note that if you use a tool to auto-populate the web form’s fields, this will populate the hidden ‘honeypot’ field causing the error to be thrown. If you do believe that the error message is being thrown incorrectly, I will need you to submit a case directly to support so we can investigate this.
I hope this clarifies things and additional information on this feature can be found in the following document: http://forums.adobe.com/docs/DOC-2882.
To answer your questions directly, yes, the 'Anti-bot Fraud Protection' module does render the {module_ccsecurity} module tag. When the form is viewed live, that module tag then renders the ‘honeypot’ field.
The module tag {module_error} itself cannot be modified. But you can modify the layout this tag resides in as well as the template assigned to this layout. Therefore, effectively you can assign a different template to this layout that does not include the breadcrumbs module. You can modify this layout via Site Manager > System Pages > General.
-
7. Re: Web Form Error
Liam Dilley Aug 1, 2013 6:52 PM (in response to Matt Baracz)It is inconsistant, I have had it produce the error on a basic form Matt.
-
8. Re: Web Form Error
Dave Blubaugh Aug 7, 2013 8:16 AM (in response to Matt Baracz)@Matt
Thank a bunch for the info. It cleared up my confusion. I now understand the theory of the "honeypot" field.
I removed the Anit-bot module for now. I had it on a simple form asking for only name, email, phone number, and captcha. All were required. For some reason it always threw the Anit-bot error. The field was not visible and should have been blank. I am not sure why I kept getting the error even without filling in the field. I was not using auto populate on the form. C'est la vie.
Cheers,
Dave
-
9. Re: Web Form Error
Liam Dilley Aug 7, 2013 8:56 AM (in response to Dave Blubaugh)You should be ok for the most part with the Catpcha on Dave. Do not worry about the error, it is on the cards to be fixed and hopefully soon by the Team.
They working really hard on the big migration but I am sure they will work on lots of updates to BC soon!




