Comments

Leave a response

1. Craig Knox on 27 Jan 00:10:
   

   Excellent. So far Rails 3.2 has been an AWESOME release. I’ve had no issues and I’ve really enjoyed the speed up on my huge app in development.

   Thanks!

2. Daniel Kehoe on 27 Jan 00:40:
   

   Thanks for keeping the updates coming! As a supplement to the official Ruby on Rails 3.2 Release Notes, here’s a detailed guide to Installing Rails 3.2.1 with some advice and recommendations.

3. Taybin on 27 Jan 03:52:
   

   Why put the CHANGELOG in a gist? Why not just post it right here, on the official blog?

   Nice bug fixes, btw.

4. Ricky on 27 Jan 06:14:
   
   1. Rails 3.2.1 Changelog
   • Documentation fixes and improvements
   • Allow `form.select` to accept ranges (regression)
   • `datetime_select` works with -/+ infinity dates
   • The threshold for auto EXPLAIN is ignored if there’s no logger
   • Call `to_s` on the value passed to `table_name=`, in particular symbols are supported (regression)
   • Fix possible race condition when two threads try to define attribute methods for the same class
   • Update time zone offset information
   • The deprecated ActiveSupport::Base64.decode64` calls `::Base64.decode64` now
   • Fixes uninitialized constant `ActiveSupport::TaggedLogging::ERROR`
   • Migration generation understands decimal{1.2} and decimal{1-2}, in addition to decimal{1,2}
5. Thiago Taranto on 29 Jan 18:26:
   

   Awesome! :)

6. ambien on 30 Jan 11:54:
   

   Thanks a lot for sharing this with all of us you really realize what you are speaking approximately! Bookmarked. Kindly additionally talk over with my web site =). We can have a hyperlink exchange agreement between us

7. fuck you on 01 Feb 07:08:
   

   node > rails

8. http://www.local-manchester-plumbers.co.uk on 01 Feb 19:57:
   

   ruby ruby ruby ruby

9. Chris on 09 Feb 16:48:
   

   Why has this form_for syntax been removed? :

   form_for :job, @job do |f|

   I’ve just upgraded a 3.0.3 rails app to 3.2 and most of the forms won’t work because they are in that format.

   If I change them to :

   form_for :job do |f|

   then my accepts_nested_attributes_for stops working unless I play around with attribute names.

   Is this a mistake? if not, how can I get around it? I’ve not been able to see much info about this change in the logs. Cheers

10. nir0 on 10 Feb 07:57:
    

    chris, try form_for @job where @job = Job.new or Job.find

11. Chris on 10 Feb 11:08:
    

    niro, that will only work if I have restful routes setup in my app. This app is not restful.

    By removing this particular form_for syntax it’s almost as if the restful is being forced onto us.

12. Chris on 10 Feb 12:37:
    

    So it seems the solution for a non-restful application is :

    Convert this :

    =form_for :project, project do |f|

    into this :

    =form_for project, :url=>{:action=>action_name} do |f|

    A bit ugly, but I can’t see any other option. I really hope the old syntax is put back in as this isn’t really helping anyone. Regards

13. loans on 20 Feb 08:30:
    

    Hello, Neat post. There is a problem along with your web site in internet explorer, would test this? IE still is the market chief and a good element of other folks will leave out your great writing because of this problem.