On 26 May 2011 14:13, John <[email protected]> wrote: > > > On Thu, May 26, 2011 at 8:43 AM, Walter Davis <[email protected]> wrote: >> >> Click isn't one of the REST states, so you will have to add that to your >> routes. In Rails 2.3, this looks like this: >> >> map.resources :posts, :member => { :click => :get } >> >> In Rails 3, you would do: >> >> resources :posts do >> member do >> get 'click' >> end >> end > > I have rails 3.0.7.Added a route as above but still line "<%= > button_to "New", :action => "click" %>" generate the error . > "No route matches {:controller=>"posts", :action=>"click"}"
That is the result of following advice without understanding that advice. The above syntax is explained in section 2.9.1 of the rails guide on routing and expects an id to be passed, which is not what you want. As has been stated several times you can use rake routes to see what routes you have declared, and you will see that posts/click is not one of them. If you just want a static route (which I think you do) then have a look at section 3.3 This time make sure that rake routes shows the result you expect. If you still cannot get it to work post what you have tried and what you see in rake routes. 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
