1.1.4: link_to with mixed case controller names "broken"?

Rails
1

I have a side navigation bar with links embedded in it like the
following:

<%= link_to( ‘Create Job’,
{ :controller => ‘eSimply’,
:action => ‘upload’ }) %>

This link now shows a routing exception

Recognition failed for “/eSimply/upload”

This link has worked for over through Rails 1.1.3 a month. I can only
assume that the upgrade to Rails 1.1.4 broke it.

I saw another routing exception earlier.

QUESTION: In general, if I have a controller class named FirstLast in a
file named first_last_controller.rb, should I expect that using
:controller => ‘firstLast’ should work in a link_to helper method call
or not?

Or was I using some sort of undocumented functionality that got “fixed”
in the framework?

QUESTION: I can fix this by referring to my controller in the same
case/underscore scheme as is in it’s filename. So in my example, I
would refer to ‘first_last’. Is this how it’s always supposed to have
worked?

Maybe I can help work on the regression tests for new releases of Rails
;)…

Thanks,
Wes

2

Wes G. wrote:

I have a side navigation bar with links embedded in it like the
following:

<%= link_to( ‘Create Job’,
{ :controller => ‘eSimply’,
:action => ‘upload’ }) %>

This link now shows a routing exception

Recognition failed for “/eSimply/upload”

This link has worked for over through Rails 1.1.3 a month. I can only
assume that the upgrade to Rails 1.1.4 broke it.

I saw another routing exception earlier.

QUESTION: In general, if I have a controller class named FirstLast in a
file named first_last_controller.rb, should I expect that using
:controller => ‘firstLast’ should work in a link_to helper method call
or not?

Or was I using some sort of undocumented functionality that got “fixed”
in the framework?

QUESTION: I can fix this by referring to my controller in the same
case/underscore scheme as is in it’s filename. So in my example, I
would refer to ‘first_last’. Is this how it’s always supposed to have
worked?

Maybe I can help work on the regression tests for new releases of Rails
;)…

Thanks,
Wes

Inside of routes.rb I can refer to my controller using “firstLast” but
not in link_to???

I don’t buy that inconsistency.

Wes

3

Wes G. wrote:

Wes G. wrote:

I have a side navigation bar with links embedded in it like the
following:

<%= link_to( ‘Create Job’,
{ :controller => ‘eSimply’,
:action => ‘upload’ }) %>

This link now shows a routing exception

Recognition failed for “/eSimply/upload”

This link has worked for over through Rails 1.1.3 a month. I can only
assume that the upgrade to Rails 1.1.4 broke it.

I saw another routing exception earlier.

QUESTION: In general, if I have a controller class named FirstLast in a
file named first_last_controller.rb, should I expect that using
:controller => ‘firstLast’ should work in a link_to helper method call
or not?

Or was I using some sort of undocumented functionality that got “fixed”
in the framework?

QUESTION: I can fix this by referring to my controller in the same
case/underscore scheme as is in it’s filename. So in my example, I
would refer to ‘first_last’. Is this how it’s always supposed to have
worked?

Maybe I can help work on the regression tests for new releases of Rails
;)…

Thanks,
Wes

Inside of routes.rb I can refer to my controller using “firstLast” but
not in link_to???

I don’t buy that inconsistency.

Wes

Sorry, let me be more plain.

What I’ve discovered is that you can refer to mixed case (two-word)
controller names as “firstLast” inside the routes.rb file and they will
map correctly, but not in the <%= link_to %> helper calls in RHTML
(which I believe implies that they would also not work in a url_for
call).

So, I will stick with the “first_last” convention even though it looks
like I’m having to know how Rails translates controller id symbols into
filenames.

Wes