Gravity Support Forums User Favorites: Bryan Hoffman

Gravity Support Forums User Favorites: Bryan Hoffman bryan-hoffman Gravity Support Forums User Favorites: Bryan Hoffman en-US Sat, 04 Apr 2026 16:16:14 +0000 http://bbpress.org/?v=1.0.1 <![CDATA[Search]]> q https://legacy.forums.gravityhelp.com/search.php Kevin Flahaut on "Fieldsets" https://legacy.forums.gravityhelp.com/topic/fieldsets#post-35488 Fri, 16 Sep 2011 11:58:16 +0000 Kevin Flahaut 35488@https://legacy.forums.gravityhelp.com/ Yeah, again it's not intended to be a grouping, simply a heading to define the following set of fields. I think that point is missed here somewhere. Nonetheless, glad that you've got a working solution. There's always room for improvement and we're constantly adding features as we go along so I'm sure we'll implement some kind of real field grouping as the plugin continues to evolve. ABT on "Fieldsets" https://legacy.forums.gravityhelp.com/topic/fieldsets#post-35487 Fri, 16 Sep 2011 11:35:12 +0000 ABT 35487@https://legacy.forums.gravityhelp.com/ Sorry, I didn't mean to imply that it's not valid HTML, but rather that it's not semantic HTML, and is therefore "faking" a section. Just because it's visually separated doesn't make it a real section -- and a section is by definition a grouping; even Gravity Forms halfway behaves as such (see below). This also probably doesn't conform to the new Accessibility guidelines as well, as screen-readers don't have the appropriate structure to go by. I did miss the fact that the conditional logic, if applied to a Section Break, does hide fields in that section (thus treating it as a group). However, using the fieldset trick you detailed earlier breaks the conditional hiding of the entire section. So in my case since I don't really care about fieldsets, existing functionality is good enough. Kevin Flahaut on "Fieldsets" https://legacy.forums.gravityhelp.com/topic/fieldsets#post-35485 Fri, 16 Sep 2011 11:00:31 +0000 Kevin Flahaut 35485@https://legacy.forums.gravityhelp.com/ @ABT The section breaks do use "correct HTML". They're simply what the name implies, section BREAKS and not intended to be groupings like fieldsets. There's no "faking" anything. We may introduce fieldsets and/or other types of groupings in a future release but for now that's not something that's a part of the core functionality. Yes, the section breaks can be used for conditional logic operations. If you want to employ actual fieldset elements in your form, you can use the HTML blocks to introduce the extra markup inline. I detailed how to do that earlier in this topic. You could use the section breaks to hinge the conditional logic, add the new markup for the fieldsets in between the section breaks and if you didn't want the actual section break headers to show, then you could simply hide those with some custom CSS. All it takes is a little bit of creativity to get it done. ABT on "Fieldsets" https://legacy.forums.gravityhelp.com/topic/fieldsets#post-35480 Fri, 16 Sep 2011 10:12:08 +0000 ABT 35480@https://legacy.forums.gravityhelp.com/ The immediate benefit of actual fieldsets is using it with the "Conditional Logic" behavior -- unless I'm missing something, there's no way to hide an entire section with just one "if another field is X". You have to apply the conditional to each field individually, right? Couldn't you just have the "Section Break" field use correct HTML? Instead of faking a new section with another <code>li</code>, have it instead start a <code>fieldset</code>. Then, however you have it applying conditional logic (I'm guessing the field id? "field_id_xyz"?), put that identifier in the fieldset tag, so it will show/hide the entire block. Kevin Flahaut on "Fieldsets" https://legacy.forums.gravityhelp.com/topic/fieldsets#post-17019 Tue, 25 Jan 2011 19:59:42 +0000 Kevin Flahaut 17019@https://legacy.forums.gravityhelp.com/ I just tested this on a new form in the latest Release Candidate version of Gravity Forms and it works perfectly. I didn't have any issues with the HTML tags being closed automatically. I tested in Firefox, Safari and Chrome on the Mac platform. I created two simple fieldsets using 3 HTML blocks - one to open the first fieldset, a second to close fieldset 1 and open fieldset 2 and a third to close the fieldsets. One thing to remember, the HTML blocks themselves are contained in the main unordered list structure, so to break everything up properly, you have to add one more step to close the containing list first, then add the other markup and in a subsequent HTML block, re-open a new UL element, etc. Here's the HTML content I added for the test form First HTML block content <pre><code></li> </ul> <fieldset id="fieldset_1"> <legend>Fieldset 1</legend> <ul class="gform_fields"></code></pre> Put form fields for the first fieldset here... Second HTML block content <pre><code></li> </ul> </fieldset> <fieldset id="fieldset_2"> <legend>Fieldset 2</legend> <ul class="gform_fields"></code></pre> Put form fields for the second fieldset here... Third HTML block content - includes some inline styles for the example <pre><code></li> </ul> </fieldset> <style type="text/css"> fieldset {border:1px solid #ccc; padding:20px; margin-bottom:30px;} fieldset legend {font-weight:bold; background:#fff; display:block; padding: 4px; border:1px solid #ccc; margin-top:-10px;} </style></code></pre> You can see my test here... screenshot: <a href="http://rkt.gs/1o" rel="nofollow">http://rkt.gs/1o</a> and you can download the XML export of my test form here: <a href="http://dl.dropbox.com/u/688846/gravityhelp/fieldset_test/gravityforms-fieldset-test-export-2011-01-25.xml" rel="nofollow">Download Form</a> Kevin Flahaut on "Fieldsets" https://legacy.forums.gravityhelp.com/topic/fieldsets#post-17012 Tue, 25 Jan 2011 19:00:44 +0000 Kevin Flahaut 17012@https://legacy.forums.gravityhelp.com/ I've implemented fieldsets several times before using the HTML blocks and didn't have any problems with tags auto-closing. I will test again and let you know what I come up with. gmdillon on "Fieldsets" https://legacy.forums.gravityhelp.com/topic/fieldsets#post-17010 Tue, 25 Jan 2011 18:45:54 +0000 gmdillon 17010@https://legacy.forums.gravityhelp.com/ Just adding my support for this feature request. Or at the very least the ability to stop the inline html from auto closing my tags. bchurby on "Fieldsets" https://legacy.forums.gravityhelp.com/topic/fieldsets#post-16788 Fri, 21 Jan 2011 15:02:20 +0000 bchurby 16788@https://legacy.forums.gravityhelp.com/ Inline HTML would be a simple solution except the parser closes the fieldset and does not allow the user to place form elements between two inline html elements as open/close. Kevin Flahaut on "wizard plugin for gravity forms" https://legacy.forums.gravityhelp.com/topic/wizard-plugin-for-gravity-forms#post-12326 Tue, 09 Nov 2010 08:49:29 +0000 Kevin Flahaut 12326@https://legacy.forums.gravityhelp.com/ Tim Theres no option to put the progressbar at the bottom. The only options are selecting the style, displaying the alternate steps or not displaying anything. We originally tried starting the bar at 0 on the first page but in tests, it proved more confusing to people when the last step (confirmation) never got to 100%. You can always add an HTML block to the end of each page and recreate the progressbar manually. Copy the markup, set the percentage (defined by inline style) to your preference and you're good to go. <pre><code><div class="gf_progressbar_wrapper" id="gf_progressbar_wrapper_4"> <h3 class="gf_progressbar_title">Step 1 of 5 - Contact Information</h3> <div class="gf_progressbar"> <div style="width: 20%;" class="gf_progressbar_percentage percentbar_orange">20%</div> </div> </div></code></pre> Tim on "wizard plugin for gravity forms" https://legacy.forums.gravityhelp.com/topic/wizard-plugin-for-gravity-forms#post-12317 Tue, 09 Nov 2010 01:38:18 +0000 Tim 12317@https://legacy.forums.gravityhelp.com/ Kevin, Looking awesome! Testing and almost ready to use this live. Question - the progress bar: In my mind this should start at 0% and progress should be displayed after the first part is complete. I.E. note the page mentioned. 5 part form - 20% complete shown at the next step? Also wondering if there is anything here I can configure - such as showing the progress at the bottom instead of the top. Perhaps there is a forum post on this already? Good stuff!