PLEASE NOTE: These forums are no longer utilized and are provided as an archive for informational purposes only. All support issues will be handled via email using our support ticket system. For more detailed information on this change, please see this blog post.

Bugs in my Post Submission Form

  1. Good morning GF Team.
    I’m hoping that someone can help me with some form bugs. I’ve tried and tried to figure out where they are coming from, but I’m failing badly. Anyhow, I’ve got some screenshots for you to take a look at. There are notes on the screenshots referencing the issues.
    Here’s a quick list of the bugs I’m seeing:
    -‘Page Title’ div being pushed upwards in the ‘Content’ div to the point where it becomes partially hidden and in some cases, completely hidden.
    -Divider lines being added to odd areas.
    -‘Previous’ and ‘Next’ buttons being positioned in odd places.
    -Increased padding below the ‘Previous’ and ‘Next’ buttons (only on the final page).

    The first image in this set of links is of a good page to show what a page should look like on the site.

    Thanks again for any advice. I’ve triple checked my gf classes and haven’t done any css form styling what-so-ever yet, hope that helps.

    Posted 9 years ago on Tuesday April 23, 2013 | Permalink
  2. David Peralty

    Our CSS experts in the community and on staff won't be able to do anything without a link to your active form so we can work to resolve the issue within the constraints of your selected theme.

    Posted 9 years ago on Tuesday April 23, 2013 | Permalink
  3. Stupid me...sorry about that Here is the link to the first page of the form. None of the fields are required, so no need to complete steps when skipping through the steps of the form

    Thanks again for any assistance.

    Posted 9 years ago on Wednesday April 24, 2013 | Permalink
  4. Dave, have you had a chance to check it out yet since I added a link to the form? Thanks in advance.

    Posted 9 years ago on Friday April 26, 2013 | Permalink
  5. Richard Vav

    It looks like your form is in a members area which we can't view

    Just another member of the community helping out where I can

    Posted 9 years ago on Friday April 26, 2013 | Permalink
  6. Sorry about that. I've made the page public, I'm sorry for forgetting to do that previously. Disregard a good majority of the original post, as I've already fixed a few of the things, plus I've reorganized the form fields and condensed some pages, so the images are not relevant at this point. In this post I've included the current images, with respective notes on each page of the errors. There are really only two pages with errors, and one of them is regarding errors based on conditional selections in the fields - which I outlined in the notes displayed on the images.

    Page 2 - No selection made yet:

    Page 2 - 'Single Family Home' sected:

    Also, to note that Awesome Screenshot messed up on saving the image and it doesn't include another note that I added in the bottom right. Here is the notation:
    "As well, if you select any of the fields mentioned above, which are supposed to be preset with 'Unsure' as the default you'll notice that you get the error "No results matched Unsure |", but then if you select another field and select the errored field again, you'll get the true field options."

    Page 2 - 'Condo...' selected:

    Final Page:


    Thanks again to anyone for their help. Much appreciated.

    Posted 9 years ago on Monday April 29, 2013 | Permalink
  7. Richard Vav

    To get your form footer including previous and next buttons back in the correct place try adding the following CSS to your themes stylesheet

    .gform_wrapper .gform_page_footer {
        clear: right;

    Can you confirm you definitely have 'Unsure' set as default when I view the source code that is not the case

    Just another member of the community helping out where I can

    Posted 9 years ago on Tuesday April 30, 2013 | Permalink
  8. Richard,

    Thanks for helping out. I sincerely appreciate it.

    #1 I applied your css to the stylesheet, though I don't believe it had any affect.

    #2 I am 100% positive (I just that those fields have the default of 'unsure'. I added the 'unsure' to make sure that none of the conditionals fired upon page load, such as 'Garage' = 'Yes', which triggers 'Cars' dropdown. So for example, 'Cars' is set to 'hide' if 'Garage' is set to 'unsure'. There are a few others like that, which I'm sure you can see when viewing, however, I wanted to give an example of how the conditional logic was setup.

    Let me know if you have any other thoughts on it. Thanks in advance.

    Posted 9 years ago on Wednesday May 1, 2013 | Permalink
  9. BUMP please :)

    Posted 9 years ago on Tuesday May 7, 2013 | Permalink
  10. Richard Vav

    Sorry for the delay in responding I didn't receive the email notification of your last post.

    1. Checking your page in both a chrome incognito window and a firefox private browsing window I can see that the css snippet is being applied and the footer is clearing the floats to appear below the form fields on each page as it should. If you are still seeing it float up into the fields then you may need to clear your cache to see the change.
    2. Checking the source code again I can see that 'unsure' is the default selected option so I am not sure why this isn't the case when viewing live, does the same thing happen when previewing the form from admin and does it also happen if you disable the enhanced user interface.

    Also have you tested for a plugin/theme conflict one reason I mention this is that while viewing your pages source code I did notice that the html for the form is split up onto seperate lines
    while the html for every form I have created has always been optimised and appeared like this which I believe is how the Gravity Forms plugin outputs the code


    Posted 9 years ago on Tuesday May 7, 2013 | Permalink
  11. Thanks Richard,

    I just hopped on to update this post. This theme has been a huge pain in the arse. Conflicts up the yin yang actually. I wrote a nice little javascript a conflict. I had to create 3 custom page templates with tons of html...conflicts. I had to create 3 different custom post templates for 3 different custom post types I wrote....conflicts on 1 of them.

    All in matter how "simple" & "clean" this theme appears...once you dive in the code, you find all kinds of inaccuracies and even a few inconsistencies with the code.

    I guess that's what I get for recommending the client find a theme that he likes. lol I shouldn't have let him pick it....that's what I get for trying to save a client money....MURPHY'S LAW!!!

    The form is not the problem. And yes, the 'clear: right' solution definitely did the trick (I forgot to clear the cache..midnight madness).

    I've done a test for plugin conflicts and unfortunately it wasn't that...after extensive testing and's the dang theme.

    All in all, I do appreciate your help Richard.

    Posted 9 years ago on Wednesday May 8, 2013 | Permalink