Ruby on Rails Wednesday, October 30, 2013

On 30 October 2013 11:04, Peter Hickman <peterhickman386@googlemail.com> wrote:
> I have a 3.1.1. app that is running in production and has been for several
> weeks now. I just added a new page and controller with an entry in routes.rb
>
> In development everything is just fine. But when I deploy the change to
> production I get a problem with the routes. Everything else is just fine.
>
> Started GET "/fix_scores_mappings" for 82.152.150.75 at 2013-10-30 10:12:54
> +0000
>
> ActionController::RoutingError (uninitialized constant
> FixScoresMappingController):
>
> The FixScoresMappingController exists and the output from rake routes is
> identical so I am at a loss as to what is going on.
>
> The only other thing that might be important (but given that everything
> works in development I am unconvinced) is that FixScoresMappingController
> was originally called FixSupplierMappingController and was manually renamed.

It is not a routing error, it cannot find the controller. Are you
sure you renamed the controller file and the class correctly? Have
you restarted the server?

Colin

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/CAL%3D0gLuK_NsdiaHPsC%2BGZpU2mytZ7xKeMii%3D0s9-yOWxofkJPQ%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

No comments:

Post a Comment