wrong number of arguments (5 for 4) about bootstrap_form

[potenza]

@lurkermike in rails 4.1.0, FormBuilder#new no longer accepts a proc object.

UPDATE: This change now exists in master and version 2.1.0

[lurkermike]

Yep, this fixed the error. Thank you!

[dideler]

Just tried upgrading an app from Rails 4.0 to 4.1 and I was getting the same error for all the spots where bootstrap_form_for was used. In my case, I simply had to update the bootstrap_form gem, which wasn't happening when I ran bundle update because I was limiting the version range too much in my Gemfile: gem "bootstrap_form", "~> 2.0.1"

Upgrading bootstrap_form introduced some new error related to sprockets-rails:

/home/dennis/.rbenv/versions/2.1.1/lib/ruby/gems/2.1.0/gems/sprockets-rails-2.1.2/lib/sprockets/railtie.rb:77:in `block in <class:Railtie>': uninitialized constant Sprockets::Rails::VERSION (NameError)

Will have to investigate that now.

P.S. @potenza the URL you posted is outdated (404).

[creativelycloudy]

I've had similar errors since upgrading from 4.1.0rc2 to 4.1 - found out
it was because the sprockets_better_errors gem
(https://github.com/schneems/sprockets_better_errors) has been merged
into 4.1.0.

From RailsApps/rails_layout#20 :
"This is because sanity checks from the sprockets_better_errors gem have
been merged into Rails 4.1. The intent is to reveal asset pipeline
errors that you would see in production when you run the app in
development mode."

Hope this helps.

[potenza]

@dideler Thanks for the heads up. I just edited my comment.

Let me know if you continue to run into any issues with our gem...

[jdickey]

I'm getting that problem with Rails 3.2.18, Ruby 2.0.0p481 on OS X 10.8.5. Any ideas?

[potenza]

Hi @jdickey what version of bootstrap_form are you using? We decided to only support rails 4+ with our latest release. Version 2.0.1 (https://github.com/bootstrap-ruby/rails-bootstrap-forms/tree/v2.0.1) was our last release with rails 3 support.

[jdickey]

@potenza Ah, thank you.