Databases
StackOverflow2013
Postsdbo
PORails 3 namespaced routes: how to link *from* a namespace back to the global namespace? [REVISED]
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PORails 3 namespaced routes: how to link *from* a namespace back to the global namespace? [REVISED]
    primarykey
    data
    text
    <p>I have a common layout file, used site-wide. It contains links like:</p> <pre><code>&lt;%= link_to("Home", { :controller =&gt; :home, :action =&gt; :index }) %&gt; </code></pre> <p>And other common links in the header/footer etc.</p> <p>All of my controllers are simply under the <code>app/controllers/</code> directory. But I've added a namespace for admins (to ban users etc):</p> <pre><code>namespace :admin do resources :users end </code></pre> <p>My admin namespace isn't any different in look &amp; feel, so it uses the same layout as the rest of the site. Which is causing some issues, since all of my <code>link_to</code> and <code>url_for</code> calls are being mis-interpreted as, say:</p> <pre><code>&lt;%= link_to("Home", { :controller =&gt; "admin/home", :action =&gt; :index }) %&gt; </code></pre> <p>Which crashes the app, as no such route exists. Do I have to go through all of my templates used by the layout and change the controller portion of the <code>link_to</code> with a leading slash, or is there a better way to make all of my top-level routes functional even under the admin namespace? I link out of the admin namespace into the top-level namespace for lots of things, so it would be good if I didn't really have to give any special consideration to my <code>link_to</code> calls.</p> <p>In summary, when under a namespaced controller, do you have to prefix all <code>:controller</code> parameters in <code>link_to</code> with a leading slash in order to break out of the namespace?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USd11wtq
    1. USd11wtq
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PORails 3 namespaced routes: how to link *from* a namespace back to the global namespace? [REVISED]
      1. This table or related slice is empty.
      1. VTUpMod
    1. COtry using '<real resource name>/forums' or even <real resource name>_forums_path (or whatever the named route is. I'm not putting this in an answer because it's just a guess/suggestion.
      singulars
      1. PORails 3 namespaced routes: how to link *from* a namespace back to the global namespace? [REVISED]
      1. USjaydel
    2. COBut the problem isn't linking to namespaced routes, it's linking to non-namespaced routes from inside a namespaced route, if you catch my drift? :) It's like you have to prefix all controller names in the links in your layout with a forward slash, e.g. `<%= link_to("Home", { :controller => "/home", :action => :index} %>`, otherwise it will try find a "Home" controller in the admin namespace but not even consider looking in the global namespace.
      singulars
      1. PORails 3 namespaced routes: how to link *from* a namespace back to the global namespace? [REVISED]
      1. USd11wtq
    3. COyou might consider this: http://pandejo.blogspot.com/2009/03/rails-nested-resources-tutorial.html
      singulars
      1. PORails 3 namespaced routes: how to link *from* a namespace back to the global namespace? [REVISED]
      1. USjaydel
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload