Here's the deal.. the inline class makes all of the fields run together inline and wrap as though they were a string of text. If ALL of your fields are inline, the browser is simply going to wrap them where there is room to do so. It has no idea that you're trying to start a new row, just that all of your fields are inline so it should wrap them.
What you can do is add an empty HTML block element between each "row" of fields to act as a separator. That should do the trick.
As far as the "small" class, it does work just fine. When you're not using the "gf_inline" ready class, the "small" class inputs are defined to be 25% width. Since the total form width is variable based on your content area the width of the small class will vary. If you have a full-page-width form like you do, the small field will naturally be larger than if your form was constrained to a smaller content area on the left of the page.
When using the "gf_inline" class, the small, medium and large classes are redefined to work better in conjunction with those inline fields.
You can always write your own CSS rules to redefine the width values to whatever you think looks best.
Right now the only way to duplicate fields or field groupings is to export the form in XML format and manually edit the form by copying/pasting blocks of field data. If you do that, you have to pay close attention to the field IDs. All of the field ID's need to be unique and it's always preferable to keep them sequential. If the field ID's aren't unique, your form won't work properly when you import it back into the plugin.
Posted 13 years ago on Monday June 27, 2011 |
Permalink
