results in the form thinking it should be PUTing
instead of POSTing:
form action=/threads/1/messages class=thread_edit id=thread_edit
method=postdiv style=margin:0;padding:0;display:inlineinput
name=_method type=hidden value=put /
-Mike
On May 30, 2010, at 8:05 PM, Michael Jurewitz wrote:
Hi
Hi there,
I can't seem to get form_for to work correctly with the URL I'm providing for a
set of nested resources. Here's what I'm doing in routes.rb:
resources :threads do
resources :messages
end
And then I've got the following form that I'm building as part of
Hi guys,
I'm having trouble getting named routes and form_for to play nicely in quite
the way I would expect. Here's a quick summary of what I've got going on:
Named route:
resources :thread, :class_name = forum_thread
Controller name:
forum_thread_controller
Model object:
23, 2010, at 2:52 AM, Michael Jurewitz wrote:
Hi guys,
I'm having trouble getting named routes and form_for to play nicely in quite
the way I would expect. Here's a quick summary of what I've got going on:
Named route:
resources :thread, :class_name = forum_thread
Controller
So looks like this is an issue with the PostgreSQL install that I
happened to snag. I just finished blowing everything away and
reinstalling it all from MacPorts and it's working like a charm.
Huge thanks for your hep, Gianluca!
-J
Gianluca Tessarolo wrote:
I just try and all are working
Hi there,
I'm trying to get up and running with PostgreSQL 8.4 and the Rails 3
beta. I'm running on Ruby 1.8.7 via RVM and have installed the 'pg'
gem. While I've been able to get the pg gem to successfully build,
whenever I create a new rails app, tell it to use Postgres, and execute
'rails
6 matches
Mail list logo
