I did. :S
Even GET requests go wrong. In the routes.rb:
map.resources :forums, :has_many => [:topics]
And doing a GET on (the existing) forums/1/topics gets routed to:
Processing ForumsController#1 (for 127.0.0.1 at 2009-03-17 10:10:29)
[GET]
Parameters: {"id"=>"topics"}
This is very strange.
On Mar 17, 10:07 am, Conrad Taylor <[email protected]> wrote:
> On Tue, Mar 17, 2009 at 2:04 AM, Harm <[email protected]> wrote:
>
> > I don't think the problem is in the plugins. The only one involved in
> > routing is the new_relic plugin and removing that one is not helping.
> > I was just providing this information as a possible inroad.
> > So far I tried the following:
> > - My environments.rb file is basically the same as the one in a new
> > project.
> > - My routes.rb file is being read properly.
> > - 'rake routes' returns the usual set of routes.
> > - Running the server with webrick iso mongrel does not help.
>
> > Any other hints?
>
> > Harm
>
> > On Mar 17, 9:46 am, Conrad Taylor <[email protected]> wrote:
> > > On Tue, Mar 17, 2009 at 1:27 AM, harm <[email protected]> wrote:
>
> > > > Dear all,
>
> > > > After the release of 2.3 I immediately updated my app. However routing
> > > > does no longer seem to work for me. I have no idea how this can happen
> > > > but as soon as I POST to, for example, the forums_path, the request
> > > > gets routed to ForumsController#index instead of
> > > > ForumsController#create. The same happens with nested resources. Eg
> > > > POST to forums/1/topics leads to a POST in the ForumsController#1 with
> > > > params "id" => "topics"
>
> > > > I'm using these plugins which might mess up the routing:
> > > > acts_as_list
> > > > ar_fixtures
> > > > attachment_fu_hacks
> > > > mimetype-fu
> > > > restful_authentication
> > > > smurf
> > > > acts_as_tree
> > > > attachment_fu
> > > > hoptoad_notifier
> > > > newrelic_rpm
> > > > role_requirement
>
> > > > Any help would be great.
>
> > > > Harm
>
> > > Hi, there's no certainty that plugins are compatible from release to
> > > release. If the plugin author hasn't upgraded the plugin for a release,
> > > then you have two choices:
>
> > > a) wait for the author to update the plugin
> > > b) fix it yourself
>
> > > From the list that appears above, do you know for certain which plugin is
> > > causing the problem?
>
> > > -Conrad
>
> Hi, did you update your Rails configurations by executing the following:
>
> rake rails:update
>
> -Conrad
>
>
--~--~---------~--~----~------------~-------~--~----~
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 [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---
