https://legacy.forums.gravityhelp.com/topic/html-output-1 Gravity Support Forums Topic: HTML Output en-US Sun, 19 Apr 2026 15:09:52 +0000 http://bbpress.org/?v=1.0.1 q https://legacy.forums.gravityhelp.com/search.php https://legacy.forums.gravityhelp.com/topic/html-output-1#post-350622 Fri, 28 Jun 2013 18:50:04 +0000 Rob Harrell 350622@https://legacy.forums.gravityhelp.com/ <p>Thanks for your comments, moving to feature requests. </p> https://legacy.forums.gravityhelp.com/topic/html-output-1#post-350577 Fri, 28 Jun 2013 18:18:50 +0000 Madalin Ignisca 350577@https://legacy.forums.gravityhelp.com/ <p>I'm doing the way you are presenting there currently, but I don't agree that is a friendly way of how the plugin makes the output for other users to handle. I have employees that aren't aware and understand of this tricks without explaining it in detail.</p> <p>So my point, the default output should me more friendly for users out of the box. </p> https://legacy.forums.gravityhelp.com/topic/html-output-1#post-350368 Fri, 28 Jun 2013 16:35:43 +0000 Kevin Flahaut 350368@https://legacy.forums.gravityhelp.com/ <p>Well, I would have to disagree about the limitations. if you're creative you can use the HTML fields to do just about anything. Yes, you can use them to close the parent list, introduce new containers or elements, then re-open the parent list and rock on. It takes a little bit of work and thought but it can be done fairly easily.</p> <p>I detailed how to do this a good while back.. the example was using fieldsets, but you could use divs instead. It would work the same way.</p> <p><a href="http://www.gravityhelp.com/forums/topic/fieldsets#post-17019" rel="nofollow">http://www.gravityhelp.com/forums/topic/fieldsets#post-17019</a> </p> https://legacy.forums.gravityhelp.com/topic/html-output-1#post-345336 Wed, 26 Jun 2013 03:27:58 +0000 Madalin Ignisca 345336@https://legacy.forums.gravityhelp.com/ <p>Outputting forms in an unordered list is limiting frontend developers a lot.</p> <p>In many situations we would use the HTML block to add some opening tags and close them in another one after some fields.</p> <p>But gravity forms is built so you can not do that.</p> <p>This limit is really frustrating.</p> <p>So, my ideal way for Gravity Forms to output the form is separate each filed in div's with current classes and id's, and for the HTML block to output the what's in it, filtered by WordPress content filter (so we could use some shortags when needed) and don't put this block in other tags you think about it, we want to control it. </p>