I have a link that used to work but now generates a routing error. The
link URL is a straightforward controller/action/id and of course, I have
map.connect ‘:controller/:action/:id’
in my routes.rb file.
When I click on this link, I get a routing error. What’s potentially
interesting about this URL is that the controller name is mixed case.
Class is ListManagementController, file name is list_management, and my
URL is:
/listManagement/target_lists_delete/6
Am I specifying the link name incorrectly? Is it possible that
specifying the mixed case controller name in a URL used to work but now
cannot be resolved correctly?
Should it be list_management or ListManagement?
I am pretty confident that this used to work and then stopped and I’ve
upgraded to Rails 1.1.13 and 1.1.14 since it worked.
I have a link that used to work but now generates a routing error. The
link URL is a straightforward controller/action/id and of course, I have
map.connect ‘:controller/:action/:id’
in my routes.rb file.
When I click on this link, I get a routing error. What’s potentially
interesting about this URL is that the controller name is mixed case.
Class is ListManagementController, file name is list_management, and my
URL is:
/listManagement/target_lists_delete/6
Am I specifying the link name incorrectly? Is it possible that
specifying the mixed case controller name in a URL used to work but now
cannot be resolved correctly?
Should it be list_management or ListManagement?
I am pretty confident that this used to work and then stopped and I’ve
upgraded to Rails 1.1.13 and 1.1.14 since it worked.
Thanks,
Wes
I verified that using the file name of the controller works. But I am
certain that this changed. Interestingly enough, in the routes.rb file,
I can route to a mixed case controller name with the :controller
parameter.
True, I’m not using url_for to generate this URL - it is hard-coded in
Javascript. Is that my problem?