Wednesday, November 30, 2011
On Wed, Nov 30, 2011 at 7:59 PM, Colin Law <clanlaw@googlemail.com> wrote:
On 30 November 2011 11:41, rahul chandra <richesrahul@gmail.com> wrote:You have a problem with your routes. It is interpreting sign_in as an
> My server is running but not getting anything
>
> ### In server m getting #####
> Started GET "/users/sign_in" for 127.0.0.1 at 2011-11-30 16:56:13
> +0530
> Processing by UsersController#show as HTML
> Parameters: {"id"=>"sign_in"}
id and going to the show action. You may have a route for show/id
before sign_in.
Try
rake routes
in a terminal to see what your routes are.
The browser says it's not redirecting properly so I think another probable cause
is requiring a logged in user for the action that shows the login page. You most
probably have a before_filter that checks if the user is logged in, and if not,
redirects to the log in page.
Show us your routes.rb and the result of rake routes if you cannot work it out.
Colin
--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
-------------------------------------------------------------
visit my blog at http://jimlabs.heroku.com
--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment