similar to: Edge Rails (1.1.0 RC1) and Typo Trunk

Hi all, Anyone else seen this? Although it happened while serving Rails, I figured a core dump caused by webrick should be posted to ruby-talk as well. It happened after I hit Ctrl-C to kill the webrick server, after a failed attempt to invoke a web service through a web page. Below are the last two log entries from the development.log file. Any ideas? Dan >/opt/bin/ruby

I''m getting to the point now where I really need to start trapping the errors. So from my AWDWR book, I added the following directly from the book into application.rb... def rescue_action_in_public(exception) case exception when ActiveRecord::RecordNotFound, ActionController::UnknownAction render(:file => "#{RAILS_ROOT}/public/404.html",

I have a class that is hand-coded (not generated using generator). Is there a preferred location for the file. app/components ? does it matter? Thanks, -- Posted via http://www.ruby-forum.com/.

Is it will known and accepted that before_save triggers should return true? I didn''t notice this before but now I see it in the documentation. Here is what I''m doing in my model: def before_save if self.has_album? self.visible = self.album.visible? end end That results in the expected result when album.visible? is true - but not when it is false. To make it

First off, congrats to everyone for getting Rails 2 released. A lot of work went into the release, and it''s good to see us reach this milestone. And now that the release dust has settled, I think it might be useful for us to have a retrospective and evaluate how the release went. I think the Ruby on Rails project has improved a lot this year, and this is another opportunity

Which is more appropriate? @session[] or session[]? Both seem to work. Is there a difference between which should be used in the controller vs. the view?

What is AJAX? SteveT Steve Litt Author: * Universal Troubleshooting Process courseware * Troubleshooting Techniques of the Successful Technologist * Rapid Learning: Secret Weapon of the Successful Technologist Webmaster * Troubleshooters.Com * http://www.troubleshooters.com

I am trying to access the Upload Progress feature in Action_Controller. When I add Action_Controller::Base.enable_upload_progress to my environment.rb file, and restart WEBrick, I get the following error: C:\eclipse\workspace\eSimplyOnlineRails>ruby script/server => Booting WEBrick... c:/ruby/lib/ruby/gems/1.8/gems/activesupport-1.2.5/lib/active_support/ dependencies.rb:195:in

Hello, http://dev.rubyonrails.org/wiki suggests to: Create a patch with your changes: svn diff > my_properly_named_patch.diff but how this proper name looks like? olegf

Hi guys I was following this: <a href="http://wiki.rubyonrails.com/rails/pages/LoginGenerator">tutorial</a> and everything was perfect until I run the script. I''ve got: <strong>MissingSourceFile</strong><br /> no such file to load -- user.rb <br /> RAILS_ROOT: script/../config/.. <br /> <pre><code>

What is the most elegant way to save new one-many associations? order = Order.new(:name => "My Order") order.line_items << LineItem.new(:product_id => 1, :quantity => 2) order.line_items << LineItem.new(:product_id => 2, :quantity => 5) order.save The above - which is by far the most elegant way of putting it - doesn''t work for me - the line_items

I''d really appreciate it if someone [with a decent understanding of the rails Dependencies mechanism] could help me explain the behaviour seen in this pastie. http://pastie.caboo.se/46630 The desired behaviour is simply aliasing a method in ApplicationController from a plugin while retaining automatic reloading in dev mode. The pastie is basically divided into 4 parts: - Setup of

Hi all, So in the interests of keeping a few areas of my code a bit under control, I''ve been investigating the concept of "concerned_with" as described here: http://paulbarry.com/articles/2008/08/30/concerned-with-skinny-controller-skinny-model Basically allowing me to have: /app/models/user.rb class User < ActiveRecord::Base concerned_with :something end

I''m trying to work with a many-to-many relationship, but the join table needs to have a is_primary field. What is the best way to work with this (adding / changing primary / deleting)? I understand that the :through option in Edge Rails can handle this better, but I was just wondering if there was a good way to handle this with Rails 1.0. Thanks, Kyle

I didn''t get the memo on this :P members_controller.rb:12: warning: Object#id will be deprecated; use Object#object_id Line 12 is: @member = Member.find(@current_member.id) How _should_ I be writing that line? Thanks, Joe -- Posted via http://www.ruby-forum.com/.

Hi From what I understand about documentation about require_dependency, this function will work like require but the file will be reloaded on every request to the server when in development mode. I have bootstrapped am minimal RoR project with 0.13.1 Rails. I have created a minimal Controller and hooked up it''s "index" action at the site root. I have also created a

Hi. I have want to use the following arrangement: Model < CustomClass < ActiveRecord::Base My CustomClass has a bunch of code I want to be held in common to all my models. What happens however is that if I access a controller that uses Model, it works. Then on the second view (hitting reload) I always get: TypeError (superclass mismatch for class User):

The revised patch submitted on #4748 broke the build, I''m looking to sort out why. Also note that this auto-test email didn''t make it to rails-core because it was too big (every test failed, so the resulting email was huge). I''ll patch my auto-testing script to truncate the email to no larger than a few kb. Michael Schoen wrote: > "marcel" made

I just saw Marcel''s change to assert_difference that changes the method API to take a string param that is evaled in a lambda. http://dev.rubyonrails.org/changeset/6693 I much preferred the old API, since it''s simple enough to pass a lambda. Passing a string means the lambda is in the wrong scope and doesn''t have access to objects in the test case scope. For an

I started with Ruby on Rails in the 0.13.x period, so I''m sure I missed out on a lot of history. There''s probably some good explanation for something I''ve been wondering about, but I haven''t seen it written down anywhere. Maybe someone can clue me in. I''ve always felt that one of the uglier APIs was the ActiveRecord::find() method. I call