In a fit of unoriginality, I’m writing a blog application using Ruby on Rails. My PostsController contains some code that ensures that the logged in user can only edit or delete their own posts.
I tried factoring this code out into a private method with a single argument for the flash message to display, but when I did this and tested it by editing another author’s post, I got an ActionController::DoubleRenderError – “Can only render or redirect once per action”.
How can I keep these checks DRY? The obvious approach is to use a before filter but the destroy method needs to display a different flash.
Here’s the relevant controller code:
before_filter :find_post_by_slug!, :only => [:edit, :show]
def edit
# FIXME Refactor this into a separate method
if @post.user != current_user
flash[:notice] = "You cannot edit another author’s posts."
redirect_to root_path and return
end
...
end
def update
@post = Post.find(params[:id])
# FIXME Refactor this into a separate method
if @post.user != current_user
flash[:notice] = "You cannot edit another author’s posts."
redirect_to root_path and return
end
...
end
def destroy
@post = Post.find_by_slug(params[:slug])
# FIXME Refactor this into a separate method
if @post.user != current_user
flash[:notice] = "You cannot delete another author’s posts."
redirect_to root_path and return
end
...
end
private
def find_post_by_slug!
slug = params[:slug]
@post = Post.find_by_slug(slug) if slug
raise ActiveRecord::RecordNotFound if @post.nil?
end
The before filter approach is still an ok option. You can gain access to which action was requested using the controller’s
action_namemethod.Sorry for that ternary operator in the middle there. 🙂 Naturally you can do whatever logic you like.
You can also use a method if you like, and avoid the double render by explicitly returning if it fails. The key here is to return so that you don’t double render.
You could simplify it more (in my opinion) by splitting out the different parts of behavior (authorization, handling bad authorization) like this:
Personally, I prefer to offload all of this routine work to a plugin. My personal favorite authorization plugin is Authorization. I’ve used it with great success for the last several years.
That would refactor your controller to use variations on: