Rails 1.2.3: Compatible with Ruby 1.8.6 (and other fixes)

Posted by David March 14, 2007 @ 12:27 AM

While Rails Edge continues to move forward at a rapid clip, we’ve still had the time to make sure that Rails 1.2.x stays in the game. This release irons out the few wrinkles there was between Ruby 1.8.6 and Rails 1.2.2. So now you can enjoy the latest Ruby with the latest Rails.

Besides the 1.8.6 compatibility, we’ve included a few minor fixes. Nothing major. This should be a drop-in replacement for Rails 1.2.2.

As always, you can upgrade with gems or use the latest svn tag (rel_1-2-3). Enjoy!

Posted in Releases | 45 comments

Comments

Leave a response

  1. Ken Collins on 14 Mar 00:41:

    Way to go!

    - TWRUG
  2. Jamie Hill on 14 Mar 00:43:

    The rel_1-2-3 tag doesn’t seem to exist in the repository?

  3. Michael Koziarski on 14 Mar 00:48:

    @Jamie: Should be there now

  4. Jeremy Kemper on 14 Mar 00:49:

    Changes in Ruby 1.8.6

  5. Claudio Kain on 14 Mar 01:06:

    Thanks for another great release

  6. Jamie Hill on 14 Mar 02:08:

    Michael: Thanks, perhaps I was a little eager ;)

  7. crayz on 14 Mar 04:14:

    Does breakpoint now work w/ Rails 1.2.3 & Ruby 1.8.6?

  8. Dillone Hailei Wang on 14 Mar 04:23:

    Great release! I need those fixes!

  9. Jeremy Kemper on 14 Mar 04:45:

    @crayz: no. The drb breakpointer won’t ever work again in 1.8.x, from what I can tell. We’re looking at some lo-fi alternatives that don’t rely on Binding.of_caller.

  10. Sergio Bayona on 14 Mar 06:02:

    As breakpointer replacement I use ruby-debug http://rubyforge.org/projects/ruby-debug/

    Exact same functionality as the drb breakpointer with some extra features.

    More info: www.datanoise.com/ruby-debug/

  11. Hurry on 14 Mar 07:19:

    Oh that`s nice. Is this release stable ? Have you fixed the problems with 1.1.6 ?

    Cheers – www.cadmio.org

  12. dominiek on 14 Mar 08:27:

    Haha guys, thanks for this version.

    This morning I had a failing functional test, for some reason, passing sessions to a get/post did not work:

    <hash> expected but was <nilclass>.

    After upgrading:

    0 failures, 0 errors

    Merci :)

  13. Dejan Dimic on 14 Mar 08:34:

    Thanks for the swift release. I am eager to use it right a way.

  14. Wincent Colaiuta on 14 Mar 11:45:

    sudo gem update Password: Updating installed gems… Need to update 16 gems from http://gems.rubyforge.org ................ complete Attempting remote update of actionmailer Install required dependency actionpack? [Yn] Y Install required dependency activesupport? [Yn] Y Successfully installed actionmailer-1.3.3 Successfully installed actionpack-1.13.3 Successfully installed activesupport-1.4.2 Installing ri documentation for actionmailer-1.3.3… Installing ri documentation for actionpack-1.13.3… Installing ri documentation for activesupport-1.4.2… Installing RDoc documentation for actionmailer-1.3.3… Installing RDoc documentation for actionpack-1.13.3… Installing RDoc documentation for activesupport-1.4.2… Attempting remote update of actionpack Successfully installed actionpack-1.13.3 Installing ri documentation for actionpack-1.13.3… While generating documentation for actionpack-1.13.3 ... MESSAGE: Unhandled special: Special: type=33, text=”SimpleXML” ... RDOC args:—ri—op /usr/local/lib/ruby/gems/1.8/doc/actionpack-1.13.3/ri—quiet lib (continuing with the rest of the installation) Installing RDoc documentation for actionpack-1.13.3… Attempting remote update of actionwebservice Install required dependency activerecord? [Yn] Y Successfully installed actionwebservice-1.2.3 Successfully installed activerecord-1.15.3 Installing ri documentation for actionwebservice-1.2.3… While generating documentation for actionwebservice-1.2.3 ... MESSAGE: Unhandled special: Special: type=33, text=”Action” ... RDOC args:—ri—op /usr/local/lib/ruby/gems/1.8/doc/actionwebservice-1.2.3/ri—quiet lib (continuing with the rest of the installation) Installing ri documentation for activerecord-1.15.3… While generating documentation for activerecord-1.15.3 ... MESSAGE: Unhandled special: Special: type=33, text=”The” ... RDOC args:—ri—op /usr/local/lib/ruby/gems/1.8/doc/activerecord-1.15.3/ri—main README—quiet lib README (continuing with the rest of the installation) Installing RDoc documentation for actionwebservice-1.2.3… Installing RDoc documentation for activerecord-1.15.3… Attempting remote update of activerecord Successfully installed activerecord-1.15.3 Installing ri documentation for activerecord-1.15.3… /usr/local/lib/ruby/1.8/rdoc/rdoc.rb:101:in `error’: (RDoc::RDocError) Directory /usr/local/lib/ruby/gems/1.8/doc/activerecord-1.15.3/ri already exists, but it looks like it isn’t an RDoc directory. Because RDoc doesn’t want to risk destroying any of your existing files, you’ll need to specify a different output directory name (using the —op <dir> option).

    from /usr/local/lib/ruby/1.8/rdoc/rdoc.rb:123:in `setup_output_dir'
from /usr/local/lib/ruby/1.8/rdoc/rdoc.rb:260:in `document'
from /usr/local/lib/ruby/site_ruby/1.8/rubygems/doc_manager.rb:101:in `run_rdoc'
from /usr/local/lib/ruby/site_ruby/1.8/rubygems/doc_manager.rb:85:in `install_ri'
from /usr/local/lib/ruby/site_ruby/1.8/rubygems/doc_manager.rb:42:in `generate_ri'
from /usr/local/lib/ruby/site_ruby/1.8/rubygems/gem_commands.rb:302:in `execute'
from /usr/local/lib/ruby/site_ruby/1.8/rubygems/gem_commands.rb:301:in `each'
from /usr/local/lib/ruby/site_ruby/1.8/rubygems/gem_commands.rb:301:in `execute'
 ... 6 levels...
from /usr/local/lib/ruby/site_ruby/1.8/rubygems/cmd_manager.rb:120:in `process_args'
from /usr/local/lib/ruby/site_ruby/1.8/rubygems/cmd_manager.rb:91:in `run'
from /usr/local/lib/ruby/site_ruby/1.8/rubygems/gem_runner.rb:30:in `run'
from /usr/local/bin/gem:23
  15. Sean on 14 Mar 18:30:

    To get back breakpoint functionality using ruby-debug, put:

    require ‘ruby-debug’ Debugger.start debugger

    Where you would before just put ‘breakpoint’.

    Run your code and you will get dropped into ruby-debug. Type ‘irb’ to get into the ruby prompt and you’re back in just like if you were using breakpoint.

    Cheers.

  16. Sean on 14 Mar 18:32:

    Gah, that’s:

    require ‘ruby-debug’

    Debugger.start

    debugger

    All on separate lines. Not on the same line as my comment displays above. Where’s the preview button?

  17. Vietnam tours on 15 Mar 03:46:

    Thanks for the swift release. I am eager to use it right a way.

  18. menneke on 15 Mar 08:19:

    I got the same error messages as Wincent (OS X.4.9 on 24” iMac). I’d very much like to hear what - if anything - needs to be done about that. Thanks

  19. DUH on 15 Mar 13:15:

    menneke: Try with a smaller screen!

  20. Drenk on 15 Mar 15:30:

    There are lots of people posted here who have no idea what’s going on. The guy with the nilclass error—come on, you have to know what that was.

  21. Absurd on 16 Mar 01:03:

    Drenk: So how about giving them a hand and pointing them to the right direction?

  22. ff on 16 Mar 14:32:

    hello

  23. z3cko on 16 Mar 15:48:

    is there no full changelog somewhere? the gem cannot be really checked for detailed changes. please!

  24. z3cko on 16 Mar 15:56:

    is version 1.2.3 still backwards compatible for ruby 1.8.4 and 1.8.5? please give us some more informations. which features of ruby 1.8.6 is it supporting now, that were not supported before?

  25. dharana on 16 Mar 21:01:

    Thanks for the upgrade but why isn’t there a changelog? It should be very quick to do and it would look more professional :(

  26. crysop2086@actionpack.rubyonrails.org Content-Transfer-Encoding: 7bit Content-Type: text/html Sub on 19 Mar 07:13:

    hy638@actionpack.rubyonrails.org

  27. ECU apartments in Greenville on 19 Mar 18:30:

    Time to upgrade. What does ^ guy’s message even mean?

  28. Rich on 19 Mar 22:21:

    Does RoR 1.2.3 work with Ruby 1.8.2?

    Debian 3.1 (Sarge) is a very popular web server platform and uses Ruby 1.8.2…

  29. Brian on 20 Mar 00:34:

    I prefer how Ruby communicates the actual changes being made to a new revision.

    http://svn.ruby-lang.org/repos/ruby/tags/v1_8_6/NEWS

    Its much easier this way vs. trying to look for all changes in the changelogs.

  30. CZ on 20 Mar 12:50:

    I’m trying to post a question to the http://weblog.rubyonrails.com/2007/2/6/in-case-you-re-having-trouble-installing-gems#respond post, but apparently comments are turned off, but I could still use help with resolving my gem install problem.

    I’m having the same problem as duder – no matter what I do ‘gem install theGemNameImInstalling’, ‘gem update’, ‘gem update—system’, clear out the source_cache file then ‘gem update’/’gem update—system’, clear out the source-cache file and the cache folder then ‘gem update’/’gem update—system’, or ‘gem update rails -y’ I get a ERROR: While executing gem ... (NoMethodError) undefined method `refresh' for #<Hash:0x#######> error.

    I’m running: ruby 1.8.6 (2007-03-13 patchlevel 0) [i686-darwin8.8.1] with Rails 1.2.3

  31. Mark on 20 Mar 17:11:

    How does one stop rails from using Unix-style naming conventions? I absolutely hate being forced to use the special character ”_” in names as it is wasted character. Is their an option to use generally-accepted conversational case naming conventions?

  32. oleg on 20 Mar 21:31:

    u better not change the ”_” cuz its what DHH says and he’s got PIMP cup and audi TT!!! also $15,000 desk and CRUDDy routes! god I love u DHH I will

  33. mixonic on 21 Mar 15:02:

    using _ causes less problems when things are translated to urls and such, places where using a space would be messy to say the least.

  34. DGM on 21 Mar 16:31:

    CZ, Wincent, menneeke -

    I fail to see the logic of why you think a blog announcement is a good place to get technical support. This blog software obviously is not designed for that sort of thing.

    OTOH, there are mailing lists, IRC, a wiki, and the trac interface which are excellent tools for getting technical support. THey are all available via the “community” and “source” links above.

  35. FX on 24 Mar 03:45:

    Home page still shows 1.2.2 instead of 1.2.3.

    Also, is 1.2.3 compatible with Ruby 1.8.2?

  36. Shoghi Effendi on 26 Mar 11:52:

    Can someone please fix how this page displays in IE7.

    Before you say – “Switch to Firefox”, remember the comments you made when you encountered IE only sites in the past.

    Thank you.

  37. FX on 27 Mar 17:30:

    This page displays fine in Opera 9.10 so I don’t think it is Firefox-only.

  38. Brook on 29 Mar 20:27:

    I’m with Shoghi Effendi,

    It’s pretty hard to sell a web framework when the homepage for it doesnt even render correctly in IE, i don’t care if it is a bug in IE.

    Sure i prefer FireFox, and i use it at home, but at work IE is our standard (albeit a bad one), and it’s really hard to sell a framework to management when the home site for the framework looks like hell.

    Seriously, how much effort would it really take? I think most web developers would agree, it’d be worth it.

  39. PhilThompson on 29 Mar 22:23:

    There is also a forum:

    http://www.railsforum.com/

    :)

  40. Matt on 30 Mar 08:23:

    Brook/Shoghi:

    why don’t you submit a patch if it is so little effort instead of whining?

    PS the page looks good in Safari too…

  41. Irfy on 30 Mar 19:07:

    @Matt: The patch is in fact so trivial that I am absolutely with Shoghi and Brook: the copyright div is missing a clear:both style definition. That’s all.

    I have the feeling that IE7’s confusion could have to do with the apparently overestimated statement “my float clearing technique is unstoppable” in the weblog’s rails.css, but that’s just guessing.

    You have to admit the page isn’t perfect either. The Favicon in the top-left corner and the 37signals image at the very bottom have wrong locations, should be /images/<image> instead of /support/weblog/<image>

    Perhaps an admin will read this and act accordingly.

    My 42 cents.

  42. most1831@RubyOnRails.com Content-Transfer-Encoding: quoted-printable Content-Type: text/html Subj on 04 Apr 03:20:

    hissed3948@RubyOnRails.com

  43. anand on 04 Apr 12:14:

    Hey, I had developed an ROR application with the ruby 1.8.2 version. In that, I had used the map.connect as the routing way(without parameters).

    Ex: ” map.connect ’/login’, :controller => ‘login’, :action => ‘user_login’ “

    This is also working in the ruby 1.8.6 and with rails 1.2.3.

    But passing the parameters in the routes like ” map.connect ’/login/change_password/:id’, :controller => ‘login’, :action => ‘change_password’ ,:id=>/\d+/ ” which was working in the ruby version 1.8.2 and rails version of 1.1.__ is not working in the combination of ruby 1.8.6 and rails 1.2.3.

    • Create a new application in this environment (ruby 1.8.6 and rails 1.2.3.) and this parameter passing (Ex: map.connect ”/:slug”, ,:slug=>/\d+/) works.

    I am trying to tell that the same application which used the map.connect way to pass parameters and working in Ruby 1.8.2 is not working with ruby 1.8.6 and rails 1.2.3

    can anybody suggest a solution for this

    I want the same application to be working in ruby 1.8.6

  44. Brook on 05 Apr 00:12:

    @Matt: So where exactly is the source for this website so i could submit said patch, it’s not in the svn repository.

    If it were that simple, someone would have already done it. Believe me, nothing would make me happier than to be able to show the rails site to a client and not have them laugh.

  45. Roderick van Domburg on 09 Apr 10:03:

    Users of continuous integration tools will find that using Ruby 1.8.6 will result in no longer being able to detect test suite failures. A fix has been committed to CVS but no word on a 1.8.7 release yet.

    So if you’re using continuous integration, you’re advised to stick with Ruby 1.8.5 for now.

Ruby on Rails was created by David Heinemeier Hansson, a partner at 37signals,
then extended and improved by a core team of committers and hundreds of open-source contributors.

Rails is released under the MIT license. Ruby under the Ruby License.

"Rails", "Ruby on Rails", and the Rails logo are trademarks of David Heinemeier Hansson. All rights reserved.

Sponsored by

 37signals