How to deal with inheritance issues? « Gravity Support Forums

Gravity Support Forums » Plugin Support » Gravity Forms

cnymike
Member

I've created a fairly simple form and have done no modifications to css.

The preview for the form looks great. This is what it looks like.
http://www.screencast.com/t/FHqDMaS5K5NR

The form as it displays on the actual page does not look very good, field titles are not top aligned and touching data entry boxes, things just aren't squared up very nicely. Here is what it looks like on the page.
http://www.screencast.com/t/oyMILQ4uIJy

I'm assuming this is a css inheritance issue with the theme stylesheet but I do not know the best way to deal with this. Any suggestions?

Here is the form URL http://www.award-winning-landscapes.com/contact/

Posted 12 years ago on Saturday March 31, 2012 | Permalink
Rob Harrell
Member
Yep, it's this right here:
```
[css]
.content-wrap ul.paging, .content-wrap label {
float: left;
}
```
Go ahead and drop this into your theme's stylesheet and you should be good to go:
```
[css]
.gform_wrapper .top_label .gfield_label {
float: none;
}
```
Posted 12 years ago on Saturday March 31, 2012 | Permalink
cnymike
Member

Fantastic. Thank you very much.

I wish I could get my head around CSS. I know a little but just don't work with it enough to be able to figure things like this out. It can be very frustrating. Thanks again for your quick fix.

As a general rule, would it be practical for me to drop that code into every theme stylesheet, just to play it safe?

Posted 12 years ago on Saturday March 31, 2012 | Permalink
Rob Harrell
Member

No problem at all. Well, every them is different. In your case, if you open up the style.css you will see that it instructs you to use custom.css if you need to place custom CSS - this is usually because if the theme creator updates the theme, your custom styles won't get wiped out. Much like you wouldn't want to edit our Forms.css file in the plugins folder, updates would wipe changes out.

Posted 12 years ago on Saturday March 31, 2012 | Permalink