Question

I have a double namespace situation, where my controllers look like this:

CandidateController
Candidate::PerformanceController
Candidate::Performance::ReviewController

In Rails 2, I was able to use redirect_to from the Candidate::Performance::ReviewController controller in order to redirect to an action in the CandidateController, like so:

class Candidate::Performance::ReviewController < ApplicationController

  before_filter :ensure_manager

  # ...

  def ensure_manager
    if !current_user.manager?
      flash[:warning] = t(:must_be_manager)
      redirect_to :controller => '/candidate', :action => :index
    end
  end
end

The / in controller => '/candidate' would allow Rails to redirect from app.com/performance/reviews to app.com/candidate.

However, this seems to not work the same in Rails 3.1. Instead, my redirect_to goes to app.com/candidate//candidate. What is the correct way to specify a “absolute” controller within a redirect_to hash (ie. without using a path helper)?

Update: I know this would be infinitely easier if I just use named route helpers (ie. candidate_path). Unfortunately, there is a lot of legacy code in our codebase which doesn’t use RESTful routing and instead uses the default “catch-all” route; ie. we have a lot of actions with no named route to fallback on.

Answer 1

If anyone else runs into this problem, it seems to be a known issue (unsure whether they consider it a bug or not, given the lack of response on the issue page from anyone working on Rails).

Until they patch it (assuming they do), I’ve added the following little monkey patch into an initializer, based on the code given in the original post of that issue:

module ActionDispatch
  module Routing
    class RouteSet
      class Generator
        def use_relative_controller_with_absolute_paths!
          return if controller.starts_with?('/')
          use_relative_controller_without_absolute_paths!
        end

        alias_method_chain :use_relative_controller!, :absolute_paths
      end
    end
  end
end

Hope this can help someone else!

Update: It seems that this was fixed in Rails here.