Forum: Ruby on Rails Form posts twice - once as post and again as get. Can some o

Announcement (2017-05-07): is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see and for other Rails- und Ruby-related community platforms.
8acba6d057b3f0c2c16cca95ad36881b?d=identicon&s=25 Bakki Kudva (bakki)
on 2007-02-20 21:14
(Received via mailing list)
Hi all,

I am having a very strange problem. I have a form with a bunch of
fields for a db query of people. The person model has_many sub models
such as addresses, skills etc. The :search action uses  :include to
eager load the data from various other tables which :belong_to people.

The results page is also a form where the user can select check boxes
to the select persons from the list and then save the set.

The problem:
The form is submitted and the query processed and the results page
rendered. tail -f log shows..

First post:
Processing PersonSearchController#search (for at 2007-02-20
13:49:28) [POST]
  Parameters: {"person_search"=>{"city"=>"", "skill_id_3"=>"",
"skill_search"=>"1",...etc etc

.....normal processing happens here till....
Rendered person_search/_results (0.00915)
Rendered layouts/_footer (0.00027)
Completed in 15.63002 (0 reqs/sec) | Rendering: 0.25152 (1%) | DB:
0.02095 (0%) | 200 OK [http://localhost/person_search/search]

The strange thing is that my breakpoint in the search action hits
again immediately. And I get a second post which actually is a get.

Processing PersonSearchController#search (for at 2007-02-20
13:49:44) [GET]
  Session ID: 30519ded2f3bfa275e4cb7a2c1e67edc
  Parameters: {"action"=>"search", "controller"=>"person_search"}

There are no form params this time. This causes (500 Internal Error)

Relevant info:

A. Both the first form and the results page with the form have
auto_complete fields which work fine and actually use a dedicated

B. I am using a form_for builder  on the first form though there is no
corresponding model.

Has any one seen this behaviour? Could using a form_for for a
non_model form cause this? Any help will be greatly appreciated.


PS: I am in the process of changing over to a plain old form_tag.
This topic is locked and can not be replied to.