felixarntz
commented
8 years ago Sounds good! I would prefer the field_wrapper approach since in my opinion it describes the issue better - also there are already some properties suffixed with -layout, and I don't wanna cause confusion.
I won't have time for the rest of this year either, it has to wait until the next release. I will definitely integrate this functionality into it myself when the time comes - however I would appreciate if you submitted a pull-request to take care of it. :)
Found your plugin when trying to get cf7 to play nicely with bootstrap proved too difficult and it's a great plugin which mostly covers our requirements.
The only thing that is missing tho is for us to be able to make more advanced field layouts. By this I mean we need to be able to have the form be horizontal layout in general but be able to have multiple fields for one label.
So for instance we would like to have one label that says Address and have 4 fields in there with different column widths so the form looks more compact. Another example would be a row for date of birth with 3 dropdown fields each at 4 colums.
Having had a brief look through the code I thought of 2 possible solutions.
Either you allow each field shortcode to override the overall form layout and then add another form layout called 'none' which will cause just the field to be output without any form-group wrappings. So entering: [text* first_name field_layout:none class:col-sm-6][text* last_name field_layout:none class:col-sm-6] would output just the two fields as 6 cols each alowing you to add your own wrapping markup
Or you could add a field to just turn off the wrapping markup an leave the form_layout untouched. So following the same example as above the fields defs would look something like: [text* first_name field_wrapper:false class:col-sm-6][text* last_name field_wrapper:false class:col-sm-6]
I would have attempted the changes myself and submitted a pull-request but wont have any time this year so I might give it a go after the xmas break.