The Community forums are being phased out in favor of a new Slack group.
Add your email address below to get an invitation to join the community slack group
cannot fill in fields in Formidable contact form
Hi Formidable People,
I’ve been using a Formidable Contact Form for a while now and have never had any problems, until yesterday. One of my clients advised me that there was a problem on his site. The fields are not fillable. I tried creating a new form, but the problem remains. This is a pretty big problem as the business relies largely on receiving requests from potential customers.
Here is the link to the form page:
http://www.woodbeckpd.com
Any tips you might have to solve this will be most welcomed!
Thank you in advance,
Neil
May 2, 2017 at 7:56 pm
Seems to be working now. Was this resolved?
May 3, 2017 at 5:16 am
Hi Bobby,
I have made a full-page-width wordpress template and I wanted to put the Contact Form in a separate <div> from the main text and float it right within four columns. The problem exists when I place the form inside this <div>.
For some reason however, the contact form functions fine when placed inside the same <div> as the main text. This is fine, in terms of functionality, but not in terms of layout - on larger devices there is a lot of space wasted.
This is an unwanted compromise, so if there is any advice you could offer to help remedy this problem I would be very grateful.
Regards,
Neil
May 3, 2017 at 8:13 am
I looked at your source code and the body tag on line 101 is missing the closing bracket:
when expecting an attribute name.
<body class="home blog"
Then, there is another body tag online 131:
<body="antialiased">
I think one of these needs to be commented out.
There's two closing body tags.
Between the missing bracket and the two body tags, I would expect all kinds of odd behavior. You should have only one body tag.
May 3, 2017 at 2:08 pm
I would start with CeJay Associates suggestion.
May 3, 2017 at 3:30 pm
OK, thanks Cejay and Bobby. I can see the missing closing bracket.
Regards,
Neil
Discussion closed.