Rails - Aug 2005 - url_for()/link_to() Broken under Webrick?

After successfully getting my "productized" sites into production, I
decided it
was time to get the development environment working (i.e. through
"script/server
--site=foo").  However, when I go to run a site under Webrick, I get two
major
errors:

(0) Routes don''t seem to work properly, specifically the root-level
route gets
ignored.  Instead, ''/'' redirects to ''/_doc''.

(1) link_to() (actually url_for()) doesn''t work, as it doesn''t
seem to recognize
the current controller/action (this may be related to #0).  If I don''t
specify a
controller and an action in my link_to(), I get:

   No url can be generated for the hash {:page=>"2"}

In this case, I _can''t_ specify a controller (or action), as this code
is in a
partial to generate pager links, and is used by multiple controllers/views.


Any ideas?  Am I doing something wrong?  Thanks ...

-- Steve

On Aug 8, 2005, at 1:55 PM, Steve Sloan wrote:
> After successfully getting my "productized" sites into
production,
> I decided it was time to get the development environment working  
> (i.e. through "script/server --site=foo").  However, when I go to
> run a site under Webrick, I get two major errors:
>
> (0) Routes don''t seem to work properly, specifically the
root-level
> route gets ignored.  Instead, ''/'' redirects to
''/_doc''.
>
> (1) link_to() (actually url_for()) doesn''t work, as it
doesn''t seem
> to recognize the current controller/action (this may be related to  
> #0).  If I don''t specify a controller and an action in my link_to 
> (), I get:
>
>   No url can be generated for the hash {:page=>"2"}
>
> In this case, I _can''t_ specify a controller (or action), as this
> code is in a partial to generate pager links, and is used by  
> multiple controllers/views.
>
>
> Any ideas?  Am I doing something wrong?  Thanks ...
>
Are you running the rails_product and site_generator 0.5 gems?  I''ll  
try to look in to this, but it may have to be tomorrow.  Can you show  
me your routes.rb file?

Regards,
Duane Johnson
(canadaduane)