# RC routing error that was not in Beta4

**URL:** <https://www.ruby-forum.com/t/rc-routing-error-that-was-not-in-beta4/192529>\
**Category:** Rails\
**Created:** [August 1, 2010, 12:16pm UTC](https://www.ruby-forum.com/t/rc-routing-error-that-was-not-in-beta4/192529 "2010-08-01T12:16:33Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![casper\_the\_ghost](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/58956e/32.png) [@casper\_the\_ghost](https://www.ruby-forum.com/u/casper_the_ghost)\
**Post date:** [August 1, 2010, 12:16pm UTC](https://www.ruby-forum.com/t/rc-routing-error-that-was-not-in-beta4/192529/1 "2010-08-01T12:16:33Z")

</div>

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!

---

<div class="post-metadata">

**Author:** ![casper\_the\_ghost](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/58956e/32.png) [@casper\_the\_ghost](https://www.ruby-forum.com/u/casper_the_ghost)\
**Post date:** [August 1, 2010, 2:00pm UTC](https://www.ruby-forum.com/t/rc-routing-error-that-was-not-in-beta4/192529/2 "2010-08-01T14:00:09Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![casper\_the\_ghost](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/58956e/32.png) [@casper\_the\_ghost](https://www.ruby-forum.com/u/casper_the_ghost)\
**Post date:** [August 2, 2010, 12:19am UTC](https://www.ruby-forum.com/t/rc-routing-error-that-was-not-in-beta4/192529/3 "2010-08-02T00:19:25Z")

</div>

Is there a way I can lodge a ticket?

---

<div class="post-metadata">

**Author:** ![casper\_the\_ghost](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/58956e/32.png) [@casper\_the\_ghost](https://www.ruby-forum.com/u/casper_the_ghost)\
**Post date:** [August 2, 2010, 9:46am UTC](https://www.ruby-forum.com/t/rc-routing-error-that-was-not-in-beta4/192529/4 "2010-08-02T09:46:02Z")

</div>

Is rails talk not the best spot to ask questions these days?

---

<div class="post-metadata">

**Author:** ![casper\_the\_ghost](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/58956e/32.png) [@casper\_the\_ghost](https://www.ruby-forum.com/u/casper_the_ghost)\
**Post date:** [August 2, 2010, 10:02am UTC](https://www.ruby-forum.com/t/rc-routing-error-that-was-not-in-beta4/192529/5 "2010-08-02T10:02:26Z")

</div>

On 2 August 2010 08:44, removed\_email\_address@domain.invalid [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)  
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.