- livbeauchampAsked on October 12, 2017 at 09:27 PM
I have embedded a form titled 'Email the Seller' to use on our client's Equipment Listings Portal. It contains Google's Invisible noCaptchaRecaptcha validation, but today is receiving spam bot submissions. To attempt solution I removed the field, then added it again and regenerated the code.
The form is rendered via "Source Code Embed" to allowing us to pre-populate listing data values into hidden fields. We initially encountered multiple script errors due to jQuery/Prototype conflict. Rewriting jQuery for noConflict compatibility resolved the errors.
After embedding the regenerated code today a warning dialogue appeared saying "Cannot contact reCAPTCHA. Check your connection and try again." The dialogue only appeared once. Dev Tools Console shows no errors. But there is a warning that may be relevant (refer screenshot). Any thoughts or suggestions would be appreciated.
- JotForm SupportKiranAnswered on October 13, 2017 at 03:02 AM
I think there is some conflict with some scripts on the form. Since you mention prepopulating the fields to the form, it works with iframe embed too. You may add the parameters and values to the form URL in the Iframe embed code as well. Could you give it a try and get back to us if that doesn't work? We will be happy to take a look again.
- JotForm SupportEltonCrisAnswered on October 13, 2017 at 09:28 AM
Thanks for the clarification.
I tested your form here http://www.equipmentguide.co.nz/listings/2011-volvo-fh16 and it submits fine.
You're right, those tags won't work because the source is protected with its iframe.
How about passing the value through URL parameter?
This should work.
And for the styling, you can always inject CSS codes to you form http://www.jotform.com/help/117-How-to-Inject-Custom-CSS-Codes.
- livbeauchampAnswered on October 14, 2017 at 12:04 AM
Thanks for your suggestions but it doesn't address the underlying issue raised. I'm familiar with injecting custom css and, yes, url parameters could be used to populate certain values. These options we're considered and tested already, but on balance of practicality Source code embed is the superior solution within the environment the form is being used. Implementing via iframe is possible, but is harder to work with in our case. So using iframe only makes sense "if" it solves the noCaptchaRecaptcha failure advised yesterday. However, inspecting iframe-form reveals the same warning in dev tools as source-form. So it doesn't appear iframe is any different. We haven't seen any new bot activity since regenerating the source code yesterday. So perhaps that resolved it. I'll continue to monitor and advise if any further issues occur.
- JotForm SupportNik_CAnswered on October 14, 2017 at 03:23 AM
If you notice any problems please get back to us so we can investigate further.