3 ms·

I'll bite with a few guesses. What are you getting around with this routing hack? Assuming you are using Devise with the conventional HomeController, and 'root

by uxp 16y ago

I'll bite with a few guesses. What are you getting around with this routing hack? Assuming you are using Devise with the conventional HomeController, and 'root :to => "home#index"' you shouldn't have to bother with faking a resource in the url. From your /login page, your logo links to /home/index anyways. All the hashtags/anchor tags should work. I've not had a problem with it myself. The headers for /index.html return the same 404 resource as /adjhasdkj123123, so I'm rather curious. Teach me something. :)

marcamillion 16y ago
The main issue was that I didn't want the user to just see compversions.com/home/index when they are logged in. I wanted them to see compversions.com. If I have index.html - as far as I found anyway - in my public directory, all requests to compversions.com (logged in or not) will either redirect to compversions/home/index or compversions.com/index.html. So, as far as my research told me at the time (remember I am just learning Rails still, so I could be wrong anyway) was that if I wanted logged in users to see compversions.com when they are logged in and on the root_path, there couldn't be a index.html, otherwise Rails routing would default to index.html.
- seats 16y ago
  Take a look at high voltage - https://github.com/thoughtbot/high_voltage https://github.com/thoughtbot/high_voltage
  - marcamillion 16y ago
    This looks interesting, but not sure it will do what I need - which is having Rails re-route requests to index.html or root_path based on if they are logged in or not...or am I missing something ?
    - seats 16y ago
      Doesn't solve your problem directly, but it's a nice way to have static pages in your app in a manageable way. You'd want to do something along the lines of what they show in the override section and test for your authenticated session within the controller, branching appropriately.

by uxp 16y ago

marcamillion 16y ago

The main issue was that I didn't want the user to just see compversions.com/home/index when they are logged in. I wanted them to see compversions.com. If I have index.html - as far as I found anyway - in my public directory, all requests to compversions.com (logged in or not) will either redirect to compversions/home/index or compversions.com/index.html. So, as far as my research told me at the time (remember I am just learning Rails still, so I could be wrong anyway) was that if I wanted logged in users to see compversions.com when they are logged in and on the root_path, there couldn't be a index.html, otherwise Rails routing would default to index.html.

seats 16y ago
Take a look at high voltage - https://github.com/thoughtbot/high_voltage https://github.com/thoughtbot/high_voltage
- marcamillion 16y ago
  This looks interesting, but not sure it will do what I need - which is having Rails re-route requests to index.html or root_path based on if they are logged in or not...or am I missing something ?
  - seats 16y ago
    Doesn't solve your problem directly, but it's a nice way to have static pages in your app in a manageable way. You'd want to do something along the lines of what they show in the override section and test for your authenticated session within the controller, branching appropriately.