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.

Section breaks are breaking my form

  1. gietz
    Member

    I've added a section break to my form and it funked up all the alignment. Even now that it has been deleted the section break still appears and is going through the middle of the form text. Not sure how to fix this.

    Also, since there are required fields, if one is missing then the next button gets moved up in to the middle of the form. I hope there is an easier solution than starting all over.

    Check it out at: http://bit.ly/zwuJ9y

    Thanks so much for any help.

    Posted 12 years ago on Tuesday March 6, 2012 | Permalink
  2. Richard Vav
    Administrator

    Hi gietz,

    What you see showing through the middle of the phone and email field labels isn't the remnants of the section break field but the top border of the forms footer. For some reason the footer isn't clearing the floated fields above which is causing it and the buttons it contains to float up the page. I will take a closer look and come back to you later.

    Posted 12 years ago on Tuesday March 6, 2012 | Permalink
  3. Richard Vav
    Administrator

    OK the footer floating up is something I haven't come across before, it's likely something in your themes css that is causing it but I haven't found it yet however if you add the following to your stylesheet it should sort it out.

    .gform_page_footer {
    clear: both;
    }
    Posted 12 years ago on Tuesday March 6, 2012 | Permalink
  4. gietz
    Member

    It moved things around a bit but didn't fix it. Would it help to take a peak inside the theme? Thanks.

    Posted 12 years ago on Tuesday March 6, 2012 | Permalink
  5. Richard Vav
    Administrator

    Looking at your css I can't see that new rule, did you remove it? If so could you put it back in at the bottom of the style.css file so I can see how it changed things.

    Thanks,

    Posted 12 years ago on Tuesday March 6, 2012 | Permalink
  6. @richardvav's solution is the fix, see screenshot:

    http://grab.by/cf9m

    Are you placing that style in the correct place and are you running any caching plugins because I don't see that style block in your theme's stylesheet (i added the one you see in my screenshot via chrome developer tools).

    Posted 12 years ago on Tuesday March 6, 2012 | Permalink
  7. gietz
    Member

    I was using wp cache plugin...I just deactivated it. Here is a screen shot of where I am putting Richard's code but not sure I am doing it right? Am I missing something? http://bit.ly/y96jdC

    Posted 12 years ago on Tuesday March 6, 2012 | Permalink
  8. You have the numbers from the code block in there. When you hover the code block you should see an icon (first one on the left) to pop the code as plain text. Copy that and paste it over what you have there.

    Or you can just go in there and manually remove the #'s 2 and 3, then save.

    Posted 12 years ago on Tuesday March 6, 2012 | Permalink
  9. Richard Vav
    Administrator

    As Rob points out the code block line numbers are what are preventing that style from working, as a side note it's always a good idea to disable caching when developing pages as having it enabled will prevent changes from appearing until the cache is rebuilt which can be hours or days later.

    Posted 12 years ago on Tuesday March 6, 2012 | Permalink
  10. gietz
    Member

    Wow! I can't believe I missed that 2 & 3. Thanks guys for helping!!!!!!

    Posted 12 years ago on Tuesday March 6, 2012 | Permalink
  11. Richard Vav
    Administrator

    No problem, just out of interest you have quite a big chunk of css inluded in the head of the page itself, if that is on all your pages you might consider moving it to your stylesheet it might help speed up page load times.

    Posted 12 years ago on Tuesday March 6, 2012 | Permalink

This topic has been resolved and has been closed to new replies.