routes

Url helpers (e.g root_url) returns a different hostname in the app controllers vs rspec examples. I have successfully been able to set the domain for url helpers in my rails app like this: class ApplicationController < ActionController::Base def default_url_options {host: "foo.com", only_path: false} end end For example, root_url outputs "http://foo.com/" within the application but "http://example.com" in my request specs. What is the recommended way to apply those url options globally in rails 3.2 so that they affect my specs? The url options do not need to be dynamic. Amin Ariana In Feature

I'm experiencing some unusual behaviour with my Rails 4 Application. Every single-time I click on a link_to inside my views, my controllers actions are being called twice. For example: In my root_url I have this standard call for users_profile : <%= link_to('User Profile', users_profile_path, :class => "logout-button") %> When I click this link, my console shows the following output: Started GET "/users/profile" for 127.0.0.1 at 2013-11-25 20:45:53 -0200 Processing by Users::SessionsController#profile as HTML User Load (0.7ms) SELECT "users".* FROM "users" WHERE "users"."id" = 45 ORDER BY

This may be a little subjective, but I feel that best-practice must exist (or even good design when it comes to Laravel apps). Googling results in lots of things that are not to do with the actual points in this question. Say I am building a web application that has teams, which may have projects, which may have documents. Should I design the routing so that documents are within the path of the projects they belong to, which are then within the path of the teams they belong to, or keep things at a top level? As far as I can tell, there are two ends to this spectrum that are worth discussing

How to get all declared routes in codeigniter? like ex. print_r($route) Because this is the problem, if the customer registered his username as 'facebook' he will be routed to account/facebook_login and not to his profile, if i changed the order of routes, all links will be routed to customer/profile and this is a no no! So basically, instead of listing all the routes that i declare and put it into an another array or db table, i want to loop into route array and check if there is a word that has been declared already so that i can stop them to register that word as their username. this is my

I understand how to set up my own routes, but how does one handle routes that fall through the cracks of the routing table? I mean, I guess the default {controller}/{action}/{id} route could be a generic catchall, but I'm not sure if that's the way to go. I like letting my users know they've requested data/a 'page' that doesn't exist. Is this where the [HandleError] filter comes in? How does that work, exactly? If your route is not found, you want to handle it as a normal HTTP 404 error. If you only add the [HandleError] attribute to your class or action, MVC will look for an Error view in