HostingRails.com

Edit - see William's post below.  Also, you can install and freeze any version of Rails in to your application at any time. You may refer the following tutorial to do so: http://www.hostingrails.com/forums/wiki_thread/2

Hello,

I also would like to run Rails 2.0... so i put the latest Rails version in my vendor directory. The application launches OK but it doesn't understand the RESTful stuff. For example I have a resource called "products". In my routes.rb I have the following statement "map.resources :products" I can browse "host.com/products/new" without problem but when I click the "create" button, it redirects me back to the "index" method instead of creating the record using the http "POST" method. The webform looks like :

<form action="/products" class="new_product" id="new_product" method="post">
...
<input id="product_submit" name="commit" type="submit" value="Create" />
</form>


Normally with Rails 2.0, clicking on the submit button should automatically call the "create" method in the Products controller. The same application works fine on my dev machine. Maybe it has something to do with the Apache server?

Can someone help me?

We are investigating whether FastCGI has compatibility issues with RESTful applications - can you try running this on Mongrel ?  

No but I'll try it later today. Thanks

I have a similar issue at hand, the RESTful create and update actions dump back to the index for one controller and work fine for another. Help please. Any workarounds?

Hi there - when you say "and work fine for another" do you mean that REST works with one controller and not for another?  Or that REST calls don't work at all?  Thus far we have not found a work around beyond upgrading to Mongrel.  Contact support and they'll hook you up.  

Are you still working on this issue? I'd like to know if it will be possible in the future to deploy Rails 2.0 RESTful applications with fastcgi.

Thanks

Frank, yes - we're working on it.  This is a high priority issue for us.  

William, yes I mean that REST delete and update actions work fine for one controller and don't work at all for another controller in the same app

Edgerunner, ok that is interesting.  What is the difference between the two controllers?  Can you post into the help desk with the path to those controllers and I'll take a look and update here as soon as we find the answer?  Thanks.