The 'new' action creates 3 empty models and displays the form to fill
in the properties for the 3 new objects (all from 1 form).
Create is followed from new to save the objects to the db etc via post
as expected.
So I suppose the best idea would be to find a way to make the
Ajax.Updater run via :get instead of :post. So I may keep my proper
RESTful resources.
The script for the Ajax.updater is:
function reloadPane(pane, src) {
new Ajax.Updater(pane, src, {asynchronous:1, evalScripts:true,
onLoading:function(request){pane.innerHTML='<img alt="Wait" src="/
images/spinner.gif" style="vertical-align:-3px" /> Loading...'}})
}
method:'delete'
I tried using:
function reloadPane(pane, src) {
new Ajax.Updater(pane, src, {asynchronous:1, evalScripts:true,
method:delete, onLoading:function(request){pane.innerHTML='<img
alt="Wait" src="/images/spinner.gif" style="vertical-align:-3px" />
Loading...'}})
}
This didn't work but just now I found an example with:
method:'delete' . Maybe the lack of quotes is what killed the script.
I'll try that as soon as I get home and post back.
Thanks for the help Jeffrey!
On Nov 26, 9:49 am, "Jeffrey L. Taylor" <
r...@abluz.dyndns.org> wrote:
> Brian,
>
> You are running into Rails/RESTful convention. In those conventions, the
> new action is a GET that returns the form for a new object. The create action
> expects a POST with the data for the new object. If this is not the semantics
> of your app or controller, either don't use 'map.resources' which does conform
> to the Rails/RESTful way, or change your actions and routes.
>
> So what does your 'new' action do?
>
> Jeffrey
>