Understanding before and after_filter

ruby-on-rails-3 before-filter
Jason Yost picture Jason Yost · Apr 10, 2011 · Viewed 10.5k times · Source

I have the following code right after my controller class declaration

  before_filter :load_form, :except => [:create, :update, :delete]
  after_filter :load_form, :only => [:create, :update, :delete]

  def load_form
    @severities = Severity.all
    @severity = Severity.new
  end

I get the list of severities when the page loads just fine, meaning that the before_filter is working. However after calling a method such as create the list of severities always comes back as nil. I think I am probably just missing some fundamental thing about filters. Can anyone help me understand why the after_filter does not work?

Answer

Steve Jorgensen picture Steve Jorgensen · Apr 10, 2011

If you were expecting to see variables in your view that were assigned in your 'after' filter, that won't work because the filter is not executed until after your view has been completely processed.

Related questions

before_filter with parameters

I have a method that does something like this: before_filter :authenticate_rights, :only => [:show] def authenticate_rights project = Project.find(params[:id]) redirect_to signin_path unless project.hidden end I also want to use this method in …

Read More
How to "update_attributes" without executing "before_save"?

I have a before_save in my Message model defined like this: class Message < ActiveRecord::Base before_save lambda { foo(publisher); bar } end When I do: my_message.update_attributes(:created_at => ...) foo and bar are executed. Sometimes, …

Read More
before_filter with devise

I'm using Devise's built in before_filter :authenticate_user!. I want to call my own custom method in my application helper if a user fails the before filter (tries to do an action when logged out). How and where can …

Read More