I have laid out a form based on this previous topic (http://www.gravityhelp.com/forums/topic/fieldsets ). What I am having issues with is all my styling and Ready Classes are not working now after using fieldsets. Is there any easy way to get all this styling back?
Thank you,
Check to make sure you have added the class "gform_fields" to the newly created UL elements. The other styles work with inheritance from that class applied to the parent list.
Thank you for the reply, Kevin. Either I didn't understand you entirely or just entered it wrong. Following your example in the link above I had added fieldsets html blocks. Per your reply here I added class="gforms_fields" to those fieldsets. Unfortunately, I didn't see a change to the styling on the page. Did I do that correctly?
Thank you,
Jon
Can you share a link to the page on your site where we can see your form?
Sure, the form I am trying to style is here. http://cleanaspace.com/house-cleaning-estimate/
Thank you for looking at it.
This member recently posted some code which will help simplify adding fieldsets to your form: http://www.gravityhelp.com/forums/topic/field-groups#post-170538
It makes the tedious part of closing and opening the list and list items easier to deal with. Looking at the source of your form, you have the list items opened and closed in the wrong order. You can confirm this by validating the markup on the page: validator.w3.org/check?verbose=1&uri=http%3A%2F%2Fcleanaspace.com%2Fhouse-cleaning-estimate%2F
Thank you, Chris. I applied the code (open and close groups) and the styling was definitely fixed. I do still have errors per the validator because of the issue you mentioned above (can't seem to remove some tags). I also still have the html blocks with fieldsets in my form as I want the CSS styling as shown and am not sure how to enter that in the form without using the HTML blocks.
So, I have errors but not sure how big of a deal they are as the front end looks pretty much like i want it at this point.
Thanks again,
Jon
As long as it works, I would look at the validation errors as things you can improve in the future.
