rails.nerd-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
2010-Aug-01 10:15 UTC
RC routing error that was not in Beta4
In beta4 I could do this: resources :sections do get :new, :on=>:member end But not with RC If I change "new" to be something else, I can do that So it seems that "new" is now treated like a reserved word of sorts? I really need to share the new method between "sections/new" and "sections/1/new" because my structure is a tree, so it makes sense to re-use Anyone know anything about this? cheers! -- 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-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
rails.nerd-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
2010-Aug-01 11:59 UTC
Re: RC routing error that was not in Beta4
Really hoping this is a bug not a new policy I can see why "new" might want to be a reserved word in some way But in this case, I really do need rails to map the "new" path so it allows creating sub member items EG: /section/1/new/ is so much cleaner compared to /section/new/?parent=1 -- 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-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
rails.nerd-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
2010-Aug-01 22:18 UTC
Re: RC routing error that was not in Beta4
Is there a way I can lodge a ticket? -- 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-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
rails.nerd-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
2010-Aug-02 07:44 UTC
Re: RC routing error that was not in Beta4
Is rails talk not the best spot to ask questions these days? -- 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-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
On 2 August 2010 08:44, rails.nerd-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org <rails.nerd-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> Is rails talk not the best spot to ask questions these days? >You post what is a quite obscure edge question on a Sunday afternoon, and get stressed that it''s not answered by Monday morning? Looking at your question, it *might* be better placed on the rails-core forum, as that''s where the core development issues are dealt with - and they''ll point you at how to log a ticket if that''s the best course of action for you. -- 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-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.