none of the options are documented (eg :include_blank)

Most only documented in README right now.

...it seems forgot this single case: inputs_for_nested_attributes

Hi,

I has a small feature request. I was hoping you could add a :selected option for inputs :as => :check_boxes. Ideally, you could pass in a single value or an array, so that one might set multiple default selected checkboxes.

Thanks!

The following form creates invalid markup by omitting the li tags after ol when creating new fieldsets.

<% semantic_form_for(@application) do |f| %>
  <%= f.inputs :financed_amount, :finance_term %>

  <% f.inputs :for => :applicants do |af| %>
    <% af.inputs :for => :personal_details do |pdf| %>
      <%= pdf.inputs :first_name, :middle_name, :last_name, :class => "inline-group" %>
      <%= pdf.inputs :date_of_birth %>
    <% end -%>
  <% end -%>

  <%= f.buttons :commit %>
<% end -%>


<form action="/applications/3" class="formtastic application" id="edit_application_3" method="post">
  <div style="margin:0;padding:0;display:inline">
    <input name="_method" type="hidden" value="put"/>
    <input name="authenticity_token" type="hidden" value="7R4cdFo7OnloRFVe8lyocG7an/bn5ooOuGL+f2wwTh4="/>
  </div>
  <fieldset class="inputs">
    <ol>
      <li class="numeric required financed_amount" id="application_financed_amount_input">
        <label for="application_financed_amount">Financed amount<abbr title="required">*</abbr></label>
        <input id="application_financed_amount" name="application[financed_amount]" size="50" type="text" value="25000.00"/>
      </li>
      <li class="numeric required finance_term" id="application_finance_term_input">
        <label for="application_finance_term">Finance term<abbr title="required">*</abbr></label>
        <input id="application_finance_term" name="application[finance_term]" size="50" type="text" value="24"/>
      </li>
    </ol>
  </fieldset>
  <input id="application_applicants_attributes_0_id" name="application[applicants_attributes][0][id]" type="hidden" value="2"/>
  <fieldset class="inputs">
    <ol>
      <fieldset class="inputs">
        <ol>
          <fieldset class="inline-group">
            <ol>
              <li class="string required first_name" id="application_applicants_attributes_0_personal_details_attributes_first_name_input">
                <label for="application_applicants_attributes_0_personal_details_attributes_first_name">First name<abbr title="required">*</abbr></label>
                <input id="application_applicants_attributes_0_personal_details_attributes_first_name" maxlength="255" name="application[applicants_attributes][0][personal_details_attributes][first_name]" size="50" type="text" value=""/>
              </li>
              <li class="string required middle_name" id="application_applicants_attributes_0_personal_details_attributes_middle_name_input">
                <label for="application_applicants_attributes_0_personal_details_attributes_middle_name">Middle name<abbr title="required">*</abbr></label>
                <input id="application_applicants_attributes_0_personal_details_attributes_middle_name" maxlength="255" name="application[applicants_attributes][0][personal_details_attributes][middle_name]" size="50" type="text" value=""/>
              </li>
              <li class="string required last_name" id="application_applicants_attributes_0_personal_details_attributes_last_name_input">
                <label for="application_applicants_attributes_0_personal_details_attributes_last_name">Last name<abbr title="required">*</abbr></label>
                <input id="application_applicants_attributes_0_personal_details_attributes_last_name" maxlength="255" name="application[applicants_attributes][0][personal_details_attributes][last_name]" size="50" type="text" value=""/>
              </li>
            </ol>
          </fieldset>
          <fieldset class="inputs">
            <ol>
              <li class="date required date_of_birth" id="application_applicants_attributes_0_personal_details_attributes_date_of_birth_input">
                <fieldset>
                  <legend>
                    <span class="label">Date of birth<abbr title="required">*</abbr></span>
                  </legend>
                  <ol>
                    <li>
                      <label for="application_applicants_attributes_0_personal_details_attributes_date_of_birth_1i">Year</label>
                      <select id="application_applicants_attributes_0_personal_details_attributes_date_of_birth_1i" name="application[applicants_attributes][0][personal_details_attributes][date_of_birth(1i)]">
                        <option value=""/>
                        <option value="2004">2004</option>
                        <option value="2005">2005</option>
                        <option value="2006">2006</option>
                        <option value="2007">2007</option>
                        <option value="2008">2008</option>
                        <option value="2009">2009</option>
                        <option value="2010">2010</option>
                        <option value="2011">2011</option>
                        <option value="2012">2012</option>
                        <option value="2013">2013</option>
                        <option value="2014">2014</option>
                      </select>
                    </li>
                    <li>
                      <label for="application_applicants_attributes_0_personal_details_attributes_date_of_birth_2i">Month</label>
                      <select id="application_applicants_attributes_0_personal_details_attributes_date_of_birth_2i" name="application[applicants_attributes][0][personal_details_attributes][date_of_birth(2i)]">
                        <option value=""/>
                        <option value="1">January</option>
                        <option value="2">February</option>
                        <option value="3">March</option>
                        <option value="4">April</option>
                        <option value="5">May</option>
                        <option value="6">June</option>
                        <option value="7">July</option>
                        <option value="8">August</option>
                        <option value="9">September</option>
                        <option value="10">October</option>
                        <option value="11">November</option>
                        <option value="12">December</option>
                      </select>
                    </li>
                    <li>
                      <label for="application_applicants_attributes_0_personal_details_attributes_date_of_birth_3i">Day</label>
                      <select id="application_applicants_attributes_0_personal_details_attributes_date_of_birth_3i" name="application[applicants_attributes][0][personal_details_attributes][date_of_birth(3i)]">
                        <option value=""/>
                        <option value="1">1</option>
                        <option value="2">2</option>
                        <option value="3">3</option>
                        <option value="4">4</option>
                        <option value="5">5</option>
                        <option value="6">6</option>
                        <option value="7">7</option>
                        <option value="8">8</option>
                        <option value="9">9</option>
                        <option value="10">10</option>
                        <option value="11">11</option>
                        <option value="12">12</option>
                        <option value="13">13</option>
                        <option value="14">14</option>
                        <option value="15">15</option>
                        <option value="16">16</option>
                        <option value="17">17</option>
                        <option value="18">18</option>
                        <option value="19">19</option>
                        <option value="20">20</option>
                        <option value="21">21</option>
                        <option value="22">22</option>
                        <option value="23">23</option>
                        <option value="24">24</option>
                        <option value="25">25</option>
                        <option value="26">26</option>
                        <option value="27">27</option>
                        <option value="28">28</option>
                        <option value="29">29</option>
                        <option value="30">30</option>
                        <option value="31">31</option>
                      </select>
                    </li>
                  </ol>
                </fieldset>
              </li>
            </ol>
          </fieldset>
        </ol>
      </fieldset>
    </ol>
  </fieldset>
  <fieldset class="buttons">
    <ol>
      <li class="commit">
        <input class="update" id="application_submit" name="commit" type="submit" value="Save Application"/>
      </li>
    </ol>
  </fieldset>
</form>

Hi, I have a problem with the default formtastic.css in IE when using
fields which output a fieldset inside another fieldset, such as a date
field.

Other browsers have no problems, but IE (versions 7 and 8 at least)
renders the label to the right of the input.

It is fixed for me by removing line 65 of formtastic.css:

form.formtastic fieldset ol li fieldset legend { position:absolute;
width:25%; padding-top:0.1em; }

or, more specifically, removing just the position:absolute. I didn't
find any other problem caused by removing this.

Here is a test case, could you give it a run and see if you have the
same issue? Hopefully we could get it solved. Thanks.

Test case here: http://gist.github.com/217794

When using a collection we get these weird id numbers as values instead of strings

Translation file

en:
titles:

- Mr
- Ms
- Dr

f.input :title, :as=>:select, :collection=> I18n.t('titles')

This will give me options that look like this

Mr
Ms
Dr

Clearly not what I was looking for - maybe to_s needs to be called somewhere?

I have the following:

class Project
 belongs_to :company
 belongs_to :parent, :class_name => 'Project', :foreign_key => 'parent_id'
 has_many :children, :class_name => 'Project', :foreign_key => 'parent_id'
end

class Company
  has_many :projects
end

In a form for the project I have

- semantic_form_for @project do |form|
  - form.inputs :name => 'Project' do
    =form.input :parent, :group_by => :company

And it fails with

method_missing: undefined method parents for "#<Company:0x104115288>":Company)

Which is cause by the method.to_s.pluralize in the call to grouped_collection_select. The correct method to call would be projects.

I will try and make a patch for looking up the correct method.

Here's some real-world examples I've found recently:

[input] mt

[input] square meters

AU$ [input] excl. GST

These can all be "solved" with some help/hint text below the input or a verbose label, but I think we should try to figure out a better solution.

I think this is really needed for 1.0. It stucks me on daily basis now. It feels like a fundamental feature, just a simple solution would be a relief right now.

Reference: http://groups.google.com.au/group/formtastic/browse_thread/thread/9bb5d808d2a9adbf

Right now, all columns named *_id are being interpretted as association foreign keys. Formtastic should instead only treat those as foreign keys if the column really is a foreign key for an association by looking into the assocation relfections.

Hello,

I would to request a new feature, reflect the :conditions options into associations. I have a application like that:

class Company < ActiveRecord::Base
  validates_inclusion_of :company_type, :in => %w(group_company customer)
end

class Case < ActiveRecord::Base
  belongs_to :customer, :class_name => 'Company', :conditions => { 'companies.company_type' => 'customer' }
  belongs_to :company, :conditions => { 'companies.company_type' => 'group_company' }
end

And I created a form like that (using HAML):

      - semantic_form_for Case.new do |f|
        - f.inputs do
          = f.input :company, :required => false, :prompt => '- Companies'
          = f.input :customer, :required => false, :prompt => '- Customers'

        - f.buttons do
          = f.submit

But formtastic doesn't reflect the conditions. Well, I arounded that with this:

      - semantic_form_for Case.new do |f|
        - f.inputs do
          = f.input :company, :required => false, :collection => Company.all(:conditions => { :company_type => 'group_company' } }), :prompt => '- Companies'
          = f.input :customer, :required => false, :collection => Company.all(:conditions => { :company_type => 'customer' } }),, :prompt => '- Customers'

        - f.buttons do
          = f.submit

I think that is a great feature and will be very apreciated by users :)

When using f.input :foo, :as => :text I get what I'd expect, a text area.
However when using f.inputs :foo, :bar, :as => :text, I'd expect:

(either)

A) A text area
B) An error to say it won't cast both :foo and :bar as a text area (Why though?)

A tiny change would mean the world if one would like to extend your builder a bit

Could you change this line in the helper module methods
options[:builder] = @@builder in
options[:builder] ||= @@builder

this way if I make a class that extends the SemanticFormBuilder I only have to call semantic_form_for(:builder => MyOwnFormBuilder) and not lose all the classes and error proc.

Tell me please are you going to make dynamic creation of nested form fields like it's done in
http://github.com/ryanb/complex-form-examples (with Prototype) or http://github.com/timriley/complex-form-examples/tree/unobtrusive-jquery-deep-fix2 (with jQuery)?
This feature will be very useful.
Thanks!

In order to use pretty iPhone-style checkbox toggles (Look: http://awardwinningfjords.com/ ), instead of using a plain old boolean_input (which in this case makes an erroneous assumption about how I'd like my label marked up) I had to add this custom input type:

def iphone_toggle_input(method, options)
  html_options = options.delete(:input_html) || {}
  html_options = default_string_options(method).merge(html_options) if STRING_MAPPINGS.include?(type)
  self.label(method, options.slice(:label, :required)) +
  self.send("check_box", method, html_options)
end

Certainly, that wasn't a big whoop (once I've ironed out the CSS-kinks), but it'd be nice to be able to just "force" the regular "input_simple" style of label markup rather than the one boolean_input now assumes.

Discussed here:

http://groups.google.com.au/group/formtastic/browse_thread/thread/af43871efa39d28b

I use semantic_fields_for a lot to create sub-forms within my "semantic_form_for" forms. There does not appear to be any way to internationalize the inputs inside the "semantic_fields_for" blocks other than specifying the label keys manually. For example:

- semantic_form_for @registration_item do |f|
  = f.inputs :description, :link, :cost, :instructions
  = f.input :event, :collection => @events
  - semantic_fields_for :new_event do |e|
    = e.inputs :title, :event_date, :summary

I've tried adding a "new_event" key to my i18n language file under en.formtastic.labels.new_event and under en.formtastic.labels.registration_item.new_event, but neither worked.

-Thanks for the great gem/plugin

Not sure what this does in practice, but I'm 99% sure a numeric value only is not a valid XHTML class:

li_options = value_as_class ? { :class => value.to_s.downcase } : {}

Makes Nokogiri XML parser to puke too...

A prefix would solve this, but I'm not sure if that would mess upp things. Specs seems to pass with a small fix, but anyway.

In my humble experience, this is just asking for trouble. It's the cheap way to link a label to the input, which is already taken care of by the "for" attribute. You don;t wrap text inputs, why should checks get special treatment? It also makes for styling hell in IE6 (your *html hacks wont always save you)

Right now I'm working on a styling framework built around formtastic and have almost all browsers behaving nice - except you-know-who. IncompetentExploder makes the checkboxes look all hurt up, and struggling to align. It works MUCH better when those inputs are not nested.

Standards FTW

Hi,

This thread: http://groups.google.com.au/group/formtastic/browse_thread/thread/9bb5d808d2a9adbf talk about cancel button.

I write a method that I'm using into a initializer file (is a monkey patch in really) but do the proposed feature.

I know that's obstrutive solution using window.history.back() or window.location = url; but the unobstrutive solution aren't greater IMHO (create a inline form reseting all css properties of this form elements using action to proposed url and get method).

This sounds to a bad workaround.

The dev will be advised about obstrutivity and I guess that's not a problem considering dev can make the unobstrutive solution by yourself if really needed.

You will use the cancel_button method:

- form.inputs do
  = form.submit_button
  = form.cancel_button
  = form.cancel_button admin_pages_path
  = form.cancel_button admin_pages_path, { :button_html => { :class => 'pretty_button' } }
  = form.cancel_button admin_pages_path, 'Cancel updates'
  = form.cancel_button admin_pages_path, 'Cancel updates', { :button_html => { :class => 'pretty_button' } }

The default url is :back, this means, window.history.back() and the default button text is I18n.t('formtastic.cancel', :default => 'Cancel').

If you specify a url, this will be "window.location = #{url.to_json}"

I guess this solve 99.9% of cancel button cases.

See the code: http://paste.pocoo.org/show/145765/

Before:

= render "/designs/image_uploader", :f => f

After (sexier):

= f.partial "/designs/image_uploader"

This is a quite common pattern I've seen, as the new/edit forms are usually similar except for the form_for-args.

Formtastic should be smarter with handling such errors:

http://stackoverflow.com/questions/93277/what-does-activerecordmultiparameterassignmenterrors-mean

Rails is not very smart when it comes to this.

...makes more sense - text field for a collection of values (e.g. if enum is stored as a string)

Hi, could you tell me plz - why on code

- semantic_form_for :profile, :html => { :method => :put }, :url => update_profile_path do |form|

e

 - form.inputs do

e

 = form.error_messages

e e

  = form.input :female, :as => :select, :collection => [["Male", false], ["Female", true]]

e

  = form.input :birthdate, :as => :date, :start_year => 1900

= form.input :timezone, :as=> :time_zone

e

 - form.buttons do

e

 = form.commit_button "Save"

formtastic renders

    <li class="date required" id="profile_birthdate_input"><fieldset><legend><span class="label">Birthdate<abbr title="required">*</abbr></span></legend><ol><li><label for="profile_birthdate_1i">Year</label><select id="profile_birthdate_1i" name="profile[birthdate(1i)]">
    <option value="1900">1900</option>
    <option value="1901">1901</option>
    <option value="1902">1902</option>
    <option value="1903">1903</option>

    <option value="1904">1904</option>
    <option value="1905">1905</option>
    <option value="1906">1906</option>
    <option value="1907">1907</option>

........................

    <option value="2014">2014</option>
    </select>
    </li><li><label for="profile_birthdate_2i">Month</label><select id="profile_birthdate_2i" name="profile[birthdate(2i)]">
    <option value="1">114</option>

    <option value="2">97</option>
    <option value="3">110</option>
    <option value="4">115</option>
    <option value="5">108</option>
    <option value="6">97</option>
    <option value="7">116</option>

    <option value="8">105</option>
    <option value="9">111</option>
    <option value="10">110</option>
    <option value="11">32</option>
    <option value="12">109</option>
    </select>

    </li><li><label for="profile_birthdate_3i">Day</label><select id="profile_birthdate_3i" name="profile[birthdate(3i)]">
    <option value="1">1</option>
    <option value="2">2</option>
..........................

    <option value="30">30</option>
    <option value="31">31</option>
    </select>

plz have a look at year field (why ended at 2014?) and month (very strange - digits instead month names) :(

Hi, could you tell me plz - why on code

- semantic_form_for :profile, :html => { :method => :put }, :url => update_profile_path do |form|

e

 - form.inputs do

e

 = form.error_messages

e e

  = form.input :female, :as => :select, :collection => [["Male", false], ["Female", true]]

e

  = form.input :birthdate, :as => :date, :start_year => 1900

= form.input :timezone, :as=> :time_zone

e

 - form.buttons do

e

 = form.commit_button "Save"

formtastic renders

    <li class="date required" id="profile_birthdate_input"><fieldset><legend><span class="label">Birthdate<abbr title="required">*</abbr></span></legend><ol><li><label for="profile_birthdate_1i">Year</label><select id="profile_birthdate_1i" name="profile[birthdate(1i)]">
    <option value="1900">1900</option>
    <option value="1901">1901</option>
    <option value="1902">1902</option>
    <option value="1903">1903</option>

    <option value="1904">1904</option>
    <option value="1905">1905</option>
    <option value="1906">1906</option>
    <option value="1907">1907</option>

........................

    <option value="2014">2014</option>
    </select>
    </li><li><label for="profile_birthdate_2i">Month</label><select id="profile_birthdate_2i" name="profile[birthdate(2i)]">
    <option value="1">114</option>

    <option value="2">97</option>
    <option value="3">110</option>
    <option value="4">115</option>
    <option value="5">108</option>
    <option value="6">97</option>
    <option value="7">116</option>

    <option value="8">105</option>
    <option value="9">111</option>
    <option value="10">110</option>
    <option value="11">32</option>
    <option value="12">109</option>
    </select>

    </li><li><label for="profile_birthdate_3i">Day</label><select id="profile_birthdate_3i" name="profile[birthdate(3i)]">
    <option value="1">1</option>
    <option value="2">2</option>
..........................

    <option value="30">30</option>
    <option value="31">31</option>
    </select>

plz have a look at year field (why ended at 2014?) and month (very strange - digits instead month names) :(

Hi, could you tell me plz - why on code

- semantic_form_for :profile, :html => { :method => :put }, :url => update_profile_path do |form|
 - form.inputs do
 = form.error_messages
  = form.input :female, :as => :select, :collection => [["Male", false], ["Female", true]]
  = form.input :birthdate, :as => :date, :start_year => 1900
  = form.input :timezone, :as=> :time_zone
 - form.buttons do
 = form.commit_button "Save"

formtastic renders

    <li class="date required" id="profile_birthdate_input"><fieldset><legend><span class="label">Birthdate<abbr title="required">*</abbr></span></legend><ol><li><label for="profile_birthdate_1i">Year</label><select id="profile_birthdate_1i" name="profile[birthdate(1i)]">
    <option value="1900">1900</option>
    <option value="1901">1901</option>
    <option value="1902">1902</option>
    <option value="1903">1903</option>

    <option value="1904">1904</option>
    <option value="1905">1905</option>
    <option value="1906">1906</option>
    <option value="1907">1907</option>

........................

    <option value="2014">2014</option>
    </select>
    </li><li><label for="profile_birthdate_2i">Month</label><select id="profile_birthdate_2i" name="profile[birthdate(2i)]">
    <option value="1">114</option>

    <option value="2">97</option>
    <option value="3">110</option>
    <option value="4">115</option>
    <option value="5">108</option>
    <option value="6">97</option>
    <option value="7">116</option>

    <option value="8">105</option>
    <option value="9">111</option>
    <option value="10">110</option>
    <option value="11">32</option>
    <option value="12">109</option>
    </select>

    </li><li><label for="profile_birthdate_3i">Day</label><select id="profile_birthdate_3i" name="profile[birthdate(3i)]">
    <option value="1">1</option>
    <option value="2">2</option>
..........................

    <option value="30">30</option>
    <option value="31">31</option>
    </select>

plz have a look at year field (why ended at 2014?) and month (very strange - digits instead month names) :(

Per this thread on google:
http://groups.google.com/group/formtastic/browse_thread/thread/648031a11ef3e335

Fix is here:
http://github.com/lardawge/formtastic/commit/3b60fc4ab6bbda3d2c51ecf57e179dc6de4cecd2