RoR 1.1 hits primetime

**Bleys** · Mar 28, 2006, 20:36

This was already blogged about earlier today on SP's new Ruby on Rails blog... but I figured it needed some forum love.

The biggest upgrade in Rails history has finally arrived. Rails 1.1 boasts more than 500 fixes, tweaks, and features from more than 100 contributors. Most of the updates just make everyday life a little smoother, a little rounder, and a little more joyful.

http://weblog.rubyonrails.com/articl...0-other-things

(Check out SP's recent RoR article, too.

)

**xmitchx** · Mar 28, 2006, 21:19

Yes I was very excited to go to the ruby on rails weblog and find 1.1 released only 3 minutes before I visited!

(Got the first comment on it too

hehe)

It's a great release with a BUNCH of great new features, I've been playing around with a few and I'm loving it.

**XMG-Eric** · Mar 28, 2006, 23:22

Great news, already updated over here. Can't wait to fully test the new enhancements, they looks quite promising!

**tetsuo shima** · Mar 29, 2006, 03:54

Yeah Ruby is getting more and more interesting. I still stick with PHP, but I am definitly working on getting closely familiar with Ruby

.

**vgarcia** · Mar 29, 2006, 04:56

Code:

gem update rails

Hope my code doesn't break

**VoxxitDesigns** · Mar 29, 2006, 05:51

The proper upgrade technique is the following in a Terminal application:

Code:

gem install rails --include-dependencies

Happy railing

**vgarcia** · Mar 29, 2006, 13:23

Argh. I don't think the login engine has been updated to support 1.1 yet. I can't seem to get WEBrick to start up an app I wrote that uses it

Edit:

I seem to be getting a "stack level too deep" error, both when I start WEBrick and when I try to run Rake.

**Dark Tranquility** · Mar 29, 2006, 15:44

Well good news, I like the RJS new template system !! (will we say goodbye to Javascript headaches?) Integration Testing is nice too

**Simon Mackie** · Mar 29, 2006, 16:49

Unfortunately, it appears that Rails 1.1 breaks Typo (and maybe a few other Rails apps too). If your host has switched to 1.1 and broken Typo, there's advice on how to fix it here:

http://nubyonrails.com/articles/2006...ver-monitoring

**JNKlein** · Mar 29, 2006, 16:58

I used
gem install rails —include-dependencies

and got the following output:

Code:

Attempting local installation of 'rails'
Local gem file not found: rails*.gem
Attempting remote installation of 'rails'
Updating Gem source index for: http://gems.rubyforge.org
Successfully installed rails-1.1.0
Successfully installed rake-0.7.0
Successfully installed activesupport-1.3.0
Successfully installed activerecord-1.14.0
Successfully installed actionpack-1.12.0
Successfully installed actionmailer-1.2.0
Successfully installed actionwebservice-1.1.0
Installing RDoc documentation for rake-0.7.0...
Installing RDoc documentation for activesupport-1.3.0...
Installing RDoc documentation for activerecord-1.14.0...
Installing RDoc documentation for actionpack-1.12.0...
Installing RDoc documentation for actionmailer-1.2.0...
Installing RDoc documentation for actionwebservice-1.1.0...

And now my rails ap is broken:

"Application error
Rails application failed to start properly""

I don't even know where to start figuring out where this went wrong, since I didn't do anything except run 1 command.

**xmitchx** · Mar 29, 2006, 17:55

Look in the logs to see, and remove all plugins.

**JNKlein** · Mar 29, 2006, 18:10

No plugins... here is the server.log:

Code:

/usr/local/lib/ruby/gems/1.8/gems/activesupport-1.3.0/lib/active_support/dependencies.rb:112:in `const_missing': uninitialized constant LoadingModule (NameError)
	from /path/to/project/public/../config/environment.rb:66
	from /path/to/project/public/dispatch.cgi:3
[Wed Mar 29 19:32:39 2006] [error] [client 127.0.0.1] Premature end of script headers: /path/to/project/public/dispatch.cgi

**Luke Redpath** · Mar 29, 2006, 19:27

Originally Posted by vgarcia

Argh. I don't think the login engine has been updated to support 1.1 yet. I can't seem to get WEBrick to start up an app I wrote that uses it

Edit:

I seem to be getting a "stack level too deep" error, both when I start WEBrick and when I try to run Rake.

Have you updated the engines plugin (you'll need to be running off the trunk)? I was having that problem and filed a bug which was promptly fixed.

http://dev.rails-engines.org/tickets/104

**Luke Redpath** · Mar 29, 2006, 19:34

Originally Posted by Simon Mackie

Unfortunately, it appears that Rails 1.1 breaks Typo (and maybe a few other Rails apps too). If your host has switched to 1.1 and broken Typo, there's advice on how to fix it here:

http://nubyonrails.com/articles/2006...ver-monitoring

Whilst I'm surprised that Typo wasn't able to get out a 1.1 compatible release in time, its even more disconcerting that hosts would just update their Rails installation without properly investigating what would happen with popular Rails apps like Typo. There have been a lot of changes so its not surprising there are some backwards compatibility issues and I would have expected a little more caution from the likes of Dreamhost and Textdrive (or any host really). Thats just reckless.

For people having problems with their apps, may I suggest freezing your apps to Rails 1.0 by either unpacking the 1.0 gem or checking out 1.0 from the Rails repository into vendor/rails - you can then be sure that when/if your host upgrades you wont have any problems and you can investigate upgrading locally in your own time.

**vgarcia** · Mar 29, 2006, 19:52

Originally Posted by Luke Redpath

Have you updated the engines plugin (you'll need to be running off the trunk)? I was having that problem and filed a bug which was promptly fixed.

http://dev.rails-engines.org/tickets/104

Looks like that might be what I need. I'll try it out at work tomorrow

**xmitchx** · Mar 29, 2006, 20:12

Originally Posted by JNKlein

No plugins... here is the server.log:

Code:

/usr/local/lib/ruby/gems/1.8/gems/activesupport-1.3.0/lib/active_support/dependencies.rb:112:in `const_missing': uninitialized constant LoadingModule (NameError)
	from /path/to/project/public/../config/environment.rb:66
	from /path/to/project/public/dispatch.cgi:3
[Wed Mar 29 19:32:39 2006] [error] [client 127.0.0.1] Premature end of script headers: /path/to/project/public/dispatch.cgi

Try reinstalling Rails 1.1 and make sure all the dependencies are updated also...

**Devious** · Mar 30, 2006, 10:34

What does rails have over the next platform?
Is it google friendly?

**ReggieB** · Mar 31, 2006, 04:22

There's also the command:

Code:

rake rails:update

This appears to update the JavaScript files in your application. Certainly the command would only run successfully on my test system when I ran it in the application folder.

Upgrade worked fine for me! Engaging smug mode.

**Sgarissta** · Mar 31, 2006, 07:18

Originally Posted by Luke Redpath

For people having problems with their apps, may I suggest freezing your apps to Rails 1.0 by either unpacking the 1.0 gem or checking out 1.0 from the Rails repository into vendor/rails - you can then be sure that when/if your host upgrades you wont have any problems and you can investigate upgrading locally in your own time.

This is just a good idea in general. If you're running a production app, run rails out of vendor, so that your host can't do something to the rails configuration to suddenly blow you out of the water. Then when you're sure you've tested an updated version, and it works, you can update your rails copy and all will be well.

**vgarcia** · Mar 31, 2006, 08:41

Originally Posted by vgarcia

Looks like that might be what I need. I'll try it out at work tomorrow

Update: this worked for me and I am a happy person again.

**PeterW** · Mar 31, 2006, 11:04

yay for rails

**CapitalWebHost** · Mar 31, 2006, 12:03

Ok..I updated 1.1 on my personal server (only me using Rails on that). Broke almost everything. So I backed it out..everything started working. Sticking with 1.0.0 for now..don't have time to muck with it.

As for our production servers, unless we get cients begging for it, we're maintaining Ruby 1.8.4 and Rails 1.0.0 as the official production releases.

Once 1.1.0 has stabalized, we'll revisit it.

**vgarcia** · Mar 31, 2006, 12:19

Originally Posted by CapitalWebHost

As for our production servers, unless we get cients begging for it, we're maintaining Ruby 1.8.4 and Rails 1.0.0 as the official production releases.

Once 1.1.0 has stabalized, we'll revisit it.

Good idea. My host didn't upgrade yet either which is great for a Typo blog I'm in the middle of customizing

**Luke Redpath** · Mar 31, 2006, 15:00

Originally Posted by Thyrium

What does rails have over the next platform?
Is it google friendly?

Not sure what you are getting at...Rails is a development framework - it doesn't write your pages for you, thats the developers job. Google only ever sees the final HTML output and thats up to the developer.

**hpal** · Apr 11, 2006, 13:19

http://www.theserverside.com/news/th...d=32723#162562
interesting debate

User Tag List

Thread: RoR 1.1 hits primetime

Thread Tools

Display

RoR 1.1 hits primetime

Bookmarks

Bookmarks

Posting Permissions