Rails 3.1 custom controller action keeps asking for ID even when route is specified?

Per the discussion on your questions, the cause is a before/around filter interfering rather than an issue with your specific action. Your application is searching for a User so it may be authentication-related.

Per the discussion on your questions, the cause is a before/around filter interfering rather than an issue with your specific action. Your application is searching for a User, so it may be authentication-related.

I'm pretty sure it goes in the Control. This is routing information to the user. As I understand MVC this is the role of the controller.

I'm happy to be corrected if anyone can explain why this should not go in controller. – NAD May 17 at 4:04.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.