Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6671335
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 26, 20262026-05-26T03:22:35+00:00 2026-05-26T03:22:35+00:00

Since upgrading to Rails 3.1, I’ve been having a problem with my site’s routing.

  • 0

Since upgrading to Rails 3.1, I’ve been having a problem with my site’s routing. Previously, with Rails 3.0, I was able to do this in my router config:

resources :quotes, :path => ""
root :to => "quotes#index"

That would give me routes like GET /(.:format) and such, which is what I want since the index action of my QuotesController can also return data in JSON, XML and ATOM.

Now, since upgrading to Rails 3.1, the routes have been showing up like this: GET /. The (.:format) is gone, and trying to access the /.atom URL doesn’t work anymore. How can I get this functionality back?

EDIT: “rake routes CONTROLLER=quotes” outputs the following:

   about_quotes GET    /about(.:format)    {:action=>"about", :controller=>"quotes"}
     top_quotes GET    /top(.:format)      {:action=>"top", :controller=>"quotes"}
  random_quotes GET    /random(.:format)   {:action=>"random", :controller=>"quotes"}
  search_quotes GET    /search(.:format)   {:action=>"searchform", :controller=>"quotes"}
                POST   /search(.:format)   {:action=>"search", :controller=>"quotes"}
nonsense_quotes GET    /nonsense(.:format) {:action=>"nonsense", :controller=>"quotes"}
    tags_quotes GET    /tags(.:format)     {:action=>"tags", :controller=>"quotes"}
     tag_quotes GET    /tags/:id(.:format) {:action=>"tag", :controller=>"quotes"}
   stats_quotes GET    /stats(.:format)    {:action=>"stats", :controller=>"quotes"}
       up_quote GET    /:id/up(.:format)   {:action=>"up", :controller=>"quotes"}
     down_quote GET    /:id/down(.:format) {:action=>"down", :controller=>"quotes"}
         quotes GET    /                   {:action=>"index", :controller=>"quotes"}
                POST   /                   {:action=>"create", :controller=>"quotes"}
      new_quote GET    /new(.:format)      {:action=>"new", :controller=>"quotes"}
     edit_quote GET    /:id/edit(.:format) {:action=>"edit", :controller=>"quotes"}
          quote GET    /:id(.:format)      {:action=>"show", :controller=>"quotes"}
                PUT    /:id(.:format)      {:action=>"update", :controller=>"quotes"}
                DELETE /:id(.:format)      {:action=>"destroy", :controller=>"quotes"}
           root        /                   {:controller=>"quotes", :action=>"index"}
  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-26T03:22:35+00:00Added an answer on May 26, 2026 at 3:22 am

    Okay, so, I’ve decided that this was probably something that the Rails team did intentionally to discourage URLs like “/.atom” (because really, does that look like something that should happen?), so I’m now using a second route (get “latest”, :action => :index) for the format URLs (so, like, “/latest.atom”) instead.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I'm having some problem with a custom made plugin since upgrading to the newest
I've had this problem ever since upgrading to xcode 4. In the core data
This one has been driving me crazy today. Since upgrading to Grails 1.2 and
Since upgrading to Rails 3.1 I'm seeing this warning message in my development log:
Since upgrading to the latest Xcode 3.2.1 and Snow Leopard, I've been getting the
I have noticed since upgrading to iOS5 that an audio app I have been
I'm only getting this error in my app since upgrading to ios4. newsDetailController.news =
Since upgrading from mvc 2 beta 2 to rc I'm having trouble with an
Plenty of pages load since upgrading my site from MVC 1.0 but if I
Since upgrading to Rails 3.1 upgrading Chrome I've had problems using the Chrome Developer

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.