#rails3

[edgar]

How to skip all filters in controller - Rails

If you need to skip in an specific controller all the filters defined in the ApplicationController, you can do this:

class MyController < ApplicationController if Rails::VERSION::STRING > "2.3" skip_filter *_process_action_callbacks.map(&:filter) else # rails 2.3.x skip_filter filter_chain end end

[edgar]

My Pry customizations for Rails console

I'm using Pry for my Rails console, I have defined the following alias in my ~/.zshrc to start the rails console using Pry:

alias sc='./script/console --irb=pry'

The .pryrc file is analogous to the .irbrc file for IRB. You can use the .pryrc file to customize Pry.

Below is my ~/.pryrc file:

The first line configure SublimeText 3 as Pry's editor

The methods unbundled_require and load_gem allows me to load an installed gem that is not included in the current project's Gemfile. In my case I'm loading the awesome_print gem (line 45) to pretty prints Ruby objects in full color exposing their internal structure with proper indentation

And then depending on the current Rails version, I configure the Rails logger (Rails 2) or the ActiveRecord logger (Rails 3) to use the STDOUT, in order to print the SQL statements to console.

This is how it looks my Rails console with these customizations:

[dennismonsewicz]

Active Admin, Kaminari and Rails boot up

Active Admin is an extremely nice tool when you need to have a quick 'plug & play' CRUD to give to admins to help administer a website.

One of the problems I kept running into was that every time my Rails server booted up (locally, production, etc), was that Kaminari (Rails gem for pagination - used by Active Admin; https://github.com/amatsuda/kaminari) would run through each registered Active Admin model and would attempt to override any page scope (by default Kaminari uses the method name of page when referring to pagination with a model and its results).

The problem looks like this (check your rails log during bootup):

https://gist.github.com/dennismonsewicz/9beedaea835e4a687472

To fix this issue simply do the following:

https://gist.github.com/dennismonsewicz/173fbfe9d25d679134c7

Happy Hunting! Dennis

[henrikwiberg]

Getting rid of those "Can't mass-assign protected attributes.."

So with Rails 4.0.0 I also came across issues with protected attributes.

By the way. Remove 'protected_attributes' from your Gemfile in case you've added that there, to ease your transition to Rails 4.

I solved this by doing two things:

Removing my attr_accessors on the model causing trouble, in my case the User model. So the information below will exemplify a solution for a model named User.

In your controller corresponding to the model, i.e. users_controller, you put the Rails 4.0.0 way of making attributes accessible.

private def user_params     params.require(:user).permit(:password, :password_confirmation, :token) end

Placing this in your controller tells rails the same thing that attr_accessor did.

In my case there is three attributes, password, password_confirmation and token.

Good luck.

[henrikwiberg]

Heroku errors when upgrading a Rails 3 app to 4.0.0?

Upgrading to 4.0.0 from a Rails 3 app caused a bunch of issues for me.

I use Heroku and this how I solved.

The errors manifested themselves as Heroku error code:

H10 – App crashed

That means the dynos kept crashing and when that is the case, they take a 10 minutes break before trying to reboot themselves.

But as soon as they reboot, they crashed instantly and after further investigating the heroku logs revealed:

R99 – Platform error

An error on Heroku's side, but that is not the case.

It also reveals: 

app[web.1]: bash: bin/rails: No such file or directory

It turns out than when you update from a Rails 3 app you need to take some actions to ease the transition to 4.0.0. Among other things you need to run:

rake rails:update:bin

To solve the dyno's crashing.

This creates a number of bin/ directories that is required by Rails 4.0.0, but your Rails 3 app lacked.

There are a number of other steps to take but those are covered both here https://devcenter.heroku.com/articles/rails4 and here by Ryan Bates of Railscasts, http://railscasts.com/episodes/415-upgrading-to-rails-4.

[senthiljruby]

Creating live application on Heroku with Rails 3.1.3

Create a new Rails application

rails new my_app -d mysql

Code the application with your own content,

                      ..............................

.............................

Add following code in GemFile

gem 'execjs'

group :production do   gem 'therubyracer', '~> 0.9.3.beta1'   gem 'pg' end

Now run bundler without production

bundle install --without production

After this create heroku application along with stack using,

heroku create my_app --stack cedar

Now commit the code to heroku,

  git push heroku master

  Counting objects: 67, done.

Delta compression using up to 4 threads.  

Compressing objects: 100% (52/52), done.

Writing objects: 100% (67/67), 86.33 KiB, done.

Total 67 (delta 5), reused 0 (delta 0) '

-----> Heroku receiving push

-----> Rails app detected ------------------------------------------- ------------------------------------------- -------------------------------------------

[senthiljruby]

Rails 3.2.8 Installation Procedure

Installing Rails 3 for windows

  ·         Download DEVKIT

·         Extract the devkit into C:/

·         Add the bin directory to the environment variable path

·         Go to the C:/Devkit

·         ruby dk.rb  init

·         ruby dk.rb review

·         ruby dk.rb install

·         gem install rails –include-dependencies

[gom68]