search for: pharrington

Hello, When I call an action with some invalid XML or JSON data a parse exception gets raised from within Rails/Ruby (REXML or ActiveSupport::JSON). The problem that I''ve got is how to handle these exceptions. In my application_controller.rb I have the following for debugging purposes: def rescue_action_in_public(exception) respond_to do |request| request.all { render :text =>

When writing Ruby you have the option to end the file early with __END__. Anything after the __END__ is assigned to a constant called DATA which is available within the file. I recently tried using this in Rails and it didn''t work. Instead I get an uninitialized constant exception. Anyone know why? Has it been disabled in Rails? thanks Gavin

Should models call action mailers, or should those calls always originate from controllers? For example, should user.forgot_password send the email, or should the user_controller.forgot_password? Just looking for some opinions... Thanks, Tom

In irb all works fine: # irb irb(main):001:0> require ''rubygems'' => true irb(main):002:0> require ''raspell'' => true irb(main):003:0> speller = Aspell.new("ru_RU") => #<Aspell:0x7f8692c9d158> irb(main):004:0> speller.suggestion_mode = Aspell::NORMAL => "normal" irb(main):005:0>

Hi, I''m having some trouble overriding/defining the default_field_options constant without raising a warning. I''ve tried adding the code to do it in an initializer but that produces a warning (because the constant is already frozen), after some googling I found a recommendation to put it in the environment.rb file but that then that throws uninitialized constant ActionView

I''ve been having great fun trying to deploy a fresh install of rails on debian, specifically xlsuite to test it out, but my god how many more errors can I take before I give up. RAILS IS NOT NICE After battling with countless different errors from trying Ubuntu, Fedora, Windows and now Debian the list goes on and on and ON... now the latest error `load_missing_constant'':