Rails namespaced routing problem?

You don't have a configured route for EventsController, so your error is happening because some request is falling down to the default route map. Connect ':controller/:action/:id.

You don't have a configured route for EventsController, so your error is happening because some request is falling down to the default route, map. Connect ':controller/:action/:id' . This is happening because someone/something is sending a request of an HTTP method that isn't configured for your AdminEventsController.

Your admin. Resources :events, :member => { :status => :get } will match the following requests: GET /admin/events GET /admin/events/ GET /admin/events//status POST /admin/events PUT /admin/events/ DELETE /admin/events/ Anything else would fall through to the default route. So if you're seeing those ActionController::UnknownAction on this controller look for requests that are using the wrong HTTP method.

The source of your bizarre log message is almost certainly a request that was something like this: GET /admin/events/index The solution is to get rid of that default route entirely and ensure you're adding resources routes for all the controllers in the right place.

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.