Databases
StackOverflow2013
Postsdbo
POAdding url_options to url_for in Rails 3.0.11
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POAdding url_options to url_for in Rails 3.0.11
    primarykey
    data
    text
    <p>I've got a problem similar to the one in <a href="https://stackoverflow.com/questions/6100954/default-url-options-and-rails-3">default_url_options and rails 3</a>. I'm attempting to implement the solution described there in the top answer, namely:</p> <pre><code>class ApplicationController &lt; ActionController::Base def url_options { :profile =&gt; current_profile }.merge(super) end end </code></pre> <p>In routes.rb (names have been changed to protect my NDA):</p> <pre><code>scope ":profile" do match "/:comment" =&gt; "comments#show", :as =&gt; :show_comment match "/comments(/*comments)" =&gt; "comments#index", :as =&gt; :show_many_comments end </code></pre> <p>Now here's the issue I'm running into with url helpers.</p> <pre><code>show_comment_path(comment) #=&gt; "/current_profile/comment" </code></pre> <p>That works as expected. However, it breaks on routes with optional segments.</p> <pre><code>show_many_comments_path([comment1, comment2]) </code></pre> <p>yields</p> <pre><code>No route matches {:profile=&gt;[comment1, comment2], :controller=&gt;"comments", :action=&gt; "index"} </code></pre> <p>However, it <em>only</em> breaks when using positional arguments rather than named arguments. In other words:</p> <pre><code>show_many_comments_path(:comments =&gt; [comment1, comment2]) #=&gt; "/current_profile/comments/comment1/comment2" </code></pre> <p>as expected. So the only error case is using positional arguments <em>and</em> optional path segments.</p> <p>I've looked through the source code in ActionDispatch, and I can't figure out why this is happening. It looks like it should be smart enough to see that we've supplied an explicit :profile, and apply the positional argument to the remaining path segment. Any insight into why it isn't doing that, or what I'd have to do to get the behavior I want?</p> <p>Edit: I'm no longer sure it's the <em>optional</em> path segments that are causing the error, as opposed to the route globbing. I thought I had previously reproduced this error on a single optional path segment, but my latest trials have optional segments behaving differently based on whether they include a * or not. In any case, I'm still curious about this, but as a practical matter I've decided to just scrap the url_options in favor of passing around explicit parameters.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USgregates
    plurals
    1. PL
      singulars
      1. LTLinked
    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. POAdding url_options to url_for in Rails 3.0.11
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POAdding url_options to url_for in Rails 3.0.11
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POAdding url_options to url_for in Rails 3.0.11
      1. This table or related slice is empty.
      1. VTUpMod
    1. COCan you give specific version of rails you're using for this? I've tried your example on 3.2.6 and it worked for me.
      singulars
      1. POAdding url_options to url_for in Rails 3.0.11
      1. USSerge Balyuk
    2. COv. 3.0.11. It's quite possible that it's not Rails that's at fault, but some gem or existing code that I'm overlooking (I'm currently in the process of removing subdomain-fu and reworking our routes to be subdomainless). But that itself would be useful information.
      singulars
      1. POAdding url_options to url_for in Rails 3.0.11
      1. USgregates
    3. COI'm seeing the exact error you describe with 3.0.11. The good news is latest versions seem to be free from it. Works as expected on 3.2.6 and 3.2.2
      singulars
      1. POAdding url_options to url_for in Rails 3.0.11
      1. USSerge Balyuk
 

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