routes

I currently have URLs which look like this: things?category_id=6&country_id=17 and I would like to have URLs which look like this: /printer_cartridges/united_kingdom Is there a way in Rails 3, without hard coding all of the categories and countries in the router to have the URLs as I would like above, perhaps using find_by_name or the such like? What is the best way to approach this? match '/:category_slug/:country_slug', :to => 'things#index' Then you'll need to update your action to look up everything using params[:category_slug] and params[:country_slug] instead of the ids. Look at the

I spend my first couple of hours with Angular JS and I am trying to write a SPA with it. However, on changing route, the scroll position remains at its current position after changing routes. This means that if someone read through half of the text on page two, this person will end up in the middle of page when two after changing to the second page. (Given that the pages are equally long.) When I look for solutions I only find people asking for the opposite, i.e. they do not want to change the scrolling position once they change pages. However, I failed to reproduce even that. I wonder if the

I have three questions about routing in Backbone.js / Marionette.js : 1) How can I get a list of all the routes my application's routers have registered ? For example for Express.js (in Node.js) it would be app.routes . I'm trying to do the same with Backbone.js / Marionette.js but couldn't find any property or method that did this. 2) I want to clean-up my URLs and remove the hashtag "#" in front of them, I know that they trigger the Routers so how can I manage to do this ? I found the following script that prototypes the Backbone router, but it's more of a hack than a stable solution :

Is there some way to provide a default value to the url/path helpers? I have an optional scope wrapping around all of my routes: #config/routes.rb Foo::Application.routes.draw do scope "(:current_brand)", :constraints => { :current_brand => /(foo)|(bar)/ } do # ... all other routes go here end end I want users to be able to access the site using these URLs: /foo/some-place /bar/some-place /some-place For convenience, I'm setting up a @current_brand in my ApplicationController : # app/controllers/application_controller.rb class ApplicationController < ActionController::Base before_filter :set

After having watched Ryan's excellent Railcast Simple OmniAuth , I've managed to implement authentication in my app. Everything is working fine, but in my view I have links that look like this: <%= link_to 'Sign in with Twitter', '/signin/twitter' %> <%= link_to 'Sign in with Facebook', '/signin/facebook' %> I was wondering if there is an elegant way to create a named route to replace that with: <%= link_to 'Sign in with Twitter', signin_twitter_path %> <%= link_to 'Sign in with Facebook', signin_facebook_path %> or: <%= link_to 'Sign in with Twitter', signin_path(:twitter) %> <%= link_to

Several different domains names point to my app on heroku, for example foo.com and bar.com both point to the app. (We host specialized blog pages, and foo.com is the domain used by our Users who are creating web pages, and bar.com is the 'public facing' domain where the blog pages are.) All the user-editing pages have Devise authentication, and the "root" on foo.com is the User's dashboard page. And a logged-in user can preview their blog page at foo.com/reviewpage/USERID each User acount also has a unique "friendly url name" such as "acme-inc-dallas-tx" On the public-facing web page bar.com

In my Rails app I have a fairly standard has_many relationship between two entities. A Foo has zero or more Bars ; a Bar belongs to exactly one Foo . Both Foo and Bar are identified by a single integer ID value. These values are unique across all of their respective instances. Bar is existence dependent on Foo: it makes no sense to have a Bar without a Foo. There's two ways to RESTfully references instances of these classes. Given a Foo.id of "100" and a Bar.id of "200": Reference each Foo and Bar through their own "top-level" URL routes, like so: /foo/100 /bar/200 Reference Bar as a nested