Errors in another controller

Oh, sorry.
So the comment controller method looks like this:

  def new
    @comment = Comment.new(@params["comment"])
    @entry = Entry.find(@comment.entry_id)
    if @comment.save
      redirect_to :controller => "entry", :action => "show", :id => @entry.to_param
    else
      render "failed"
    end
  end

failed.rhtml would then be

<%= render :controller => "entry", :action => "show", :id => @entry.id %>

What I also tried was to write the comment controller method like this:

  def new
    @comment = Comment.new(@params["comment"])
    @entry = Entry.find(@comment.entry_id)
    @comment.save
    redirect_to :controller => "entry", :action => "show", :id => @entry.to_param
  end

/app/views/entry/show.rhtml has this in it:

      <div class="errors">
        <% if @comment -%>
        <%   unless @comment.errors.empty? -%>
        <%=    "foobar" %>
        <%   end -%>
        <% end -%>
      </div>

So how do I get @comment accessible from there? Or should I do it in a completely different way?
I hope that is enough code, at least it's all I've manipulated trying to get this to work.

Last edited by Kolja (2006-11-27 09:19:18)

It looks like the only time you are doing a redirect on the create action is when the comment saves successfully, so I'm not certain what the problem is. You may want to try this for rendering:

if @comment.save
  redirect_to :controller => "entry", :action => "show", :id => @entry.to_param
else
  render :action => 'entry/show'
end

Haven't tested rendering an action in another controller before though.

What I would do is add a "new" action to this comments controller with its own form. You can move the comments form into a partial so that code isn't duplicated. You can then render this "new" action with the errors if there is a problem. This way you don't have to worry about resetting the instance variables for the entry/show action.

You can move the common code up into a private method in ApplicationController and call it before the template. Another way is to move the custom find logic into the model so you can call it directly from the view - then the template won't rely on any code in the controller. It all depends upon your situation.