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.

.CSS Ready Class formatting error after update to 1.5

  1. ckrauskopf
    Member

    Hi,

    I recently updated from gf1.5beta1 to the final release of gf1.5 - this was a few days ago, and I regret to say that I did not check the form immediately after upgrading. Today I realized that the sections that were previously 2 and 3 column layouts using the the css ready classes were now staggered rather than side by side. I have been working on the site since then, so I can't be sure it was the update that messed up the formatting. That said, it seems like the most likely place to start looking for the problem.

    I am also using the Thesis Theme, and I know that you removed Thesis specific .css from the core gf styles in this release. I did paste the Thesis Specific code from your blog post into my custom css file, but it didn't solve the problem.

    Here is a screen shot of the form in pristine condition:

    http://bluventureinvestors.com/wp-content/uploads/2011/04/Form-Appearance-Before.jpg

    Here is the url of the live form with errors:

    http://bluventureinvestors.com/submit-a-plan/

    Thanks for your help.

    Chris

    Posted 13 years ago on Thursday April 7, 2011 | Permalink
  2. This is because the final 1.5 release removed Thesis specific hacks from the Gravity Forms stylesheet which may have caused the change. We are trying to work with the guys at DIYThemes to implement changes directly to Thesis to better handle Gravity Forms.

    This may require you to adjust some things in your Thesis custom stylesheet.

    When I inspect your code I see you have CSS being applied to this element:

    li.blue_field{}

    It sets padding on this element. The padding causing the problem is the padding-right being applied of 6px. Remove that, and it causes them to float correctly. That additional padding is what is causing the issue.

    Posted 13 years ago on Thursday April 7, 2011 | Permalink