How do you route an action to the application controller in Rails 3?

Question

I am using the gem rails3-jquery-autocomplete and had no problems with it, however I have now moved my autocomplete form into the application template and therefore the ajax calls are now being dealt by the application controller, so my routes have changed from:

home/autocomplete_category_name

and now need to have the home removed and the path from:

home_autocomplete_category_name_path

to:

autocomplete_category_name_path

Anybody got any ideas? Still learning the ins and outs of Rails so this is a dead end for me right now.

Thanks.

It would be best to post the current RoR actual code for the route in question as well as the URL that you are targeting. — jschorr, Jan 24 '11 at 03:44
Also, include your current routes by typing `rake routes` at the console in your root project directory. — raidfive, Jan 24 '11 at 07:56

Pavling · Answer 1 · 2013-08-17T14:54:48.257

34

Old post, but the accepted answer is wrong. Though the spirit of it is right - you should probably move your method to a more appropriate controller; but if you insist on having the method in application_controller.rb

# routes.rb
match '/some_route', to: 'application#some_route', as: :some_route

...will route to the 'some_route' method in application_controller.rb.

edited Aug 17 '13 at 14:54

answered Mar 21 '13 at 17:20

Pavling

3,933
1
22
25

Use `get`, `post`, etc..., instead of `match` for later versions of Rails – ecbrodie Sep 12 '19 at 18:28

score 8 · Accepted Answer · answered Jan 24 '11 at 11:35

8

URLs don't map directly to ApplicationController - only subclasses of it.

You need to move the call to autocomplete into another controller. The location of the form shouldn't make a difference, as long as you're passing the correct path when you define your text_field

answered Jan 24 '11 at 11:35

dnch

9,565
2
38
41

I have ended up doing exactly as you said, it is not an eloquent solution but it does work, thanks! – Hard-Boiled Wonderland Jan 25 '11 at 00:02
4

It's possible to route to ApplicationController if you want to - just against the convention of things – Pavling Mar 21 '13 at 17:18
1

what if i want to set that as my root path of the application ? – huzefa biyawarwala Jan 12 '16 at 04:47

score 7 · Answer 3 · answered Oct 17 '13 at 07:09

Another necro but there is a more DRY friendly way to do this, compared to pavling's solution

get :autocomplete_category_name, controller:"application"

I was trying(yesterday) to move it to the Application controller to try to reuse code better and not tie it to a specific controller. Only today did I realize that makes no sense, since the controller used to answer this call is going to be a completely different object to the controller rendering the view anyway..

Works great for generic calls that are not controller-specific. — Joshua Pinter, Nov 08 '13 at 19:54

score 1 · Answer 4 · answered Dec 21 '13 at 15:13

1

Using Rails 4, your have to use get, not match...

# routes.rb
get '/autocomplete_category_name', to: 'application#autocomplete_category_name', as: :autocomplete_category_name

answered Dec 21 '13 at 15:13

maduhaime

21
3

you don't *have* to... you *can* add a `via:` option. – Pavling Jun 03 '15 at 12:41

score 0 · Answer 5 · answered Jan 24 '11 at 10:59

0

try something like

match "home/autocomplete_category_name", "home#autocomplete_category_name", :as => "autocomplete_category_name"

answered Jan 24 '11 at 10:59

kylewelsby

4,031
2
29
35

score 0 · Answer 6 · answered May 01 '18 at 09:05

0

In Rails 4, use this:

get 'application/autocomplete_category_name', as: 'autocomplete_category_name'

You have 'autocomplete_category_name_path' to you links

answered May 01 '18 at 09:05

Artem

1

How do you route an action to the application controller in Rails 3?

6 Answers6

Linked