Databases
StackOverflow2013
Postsdbo
POHow to render two paginated and ajaxable collections in the same view?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHow to render two paginated and ajaxable collections in the same view?
    primarykey
    data
    text
    <p>In a Rails 3.2 index view I am rendering two partials.</p> <pre><code>&lt;%= render :partial =&gt; 'users/user', :locals =&gt; {:users =&gt; @happy_users} %&gt; &lt;%= render :partial =&gt; 'users/user', :locals =&gt; {:users =&gt; @sad_users} %&gt; </code></pre> <p>and in the partial </p> <pre><code>&lt;% users.each do |user| %&gt; Show some fields &lt;% end %&gt; &lt;%= will_paginate users %&gt; </code></pre> <p>The pagination is not working. </p> <p>If I alter <code>will_paginate</code> to take an instance variable, pagination works (but the wrong collection)</p> <pre><code>&lt;%= will_paginate @users %&gt; </code></pre> <p>How can I pass locals to will_paginate when the partial is called?</p> <p>(I realize that I'll also need to pass <code>:param_name</code> to get this working with two collections. For now I'm just trying to get one instance working.)</p> <p>The partial is rendered via index.js.erb</p> <pre><code>$(".ajaxable-users").html('&lt;%= escape_javascript(render("users/user")) %&gt;'); </code></pre> <p>And the controller looks like</p> <pre><code>def index @users = User.scoped.paginate(:page =&gt; params[:page], :per_page =&gt; 5) @happy_users = User.happy_scope.paginate(:page =&gt; params[:page], :per_page =&gt; 5) @sad_users = User.happy_scope.paginate(:page =&gt; params[:page], :per_page =&gt; 5) respond_to do |format| format.html # index.html.erb format.xml { render :xml =&gt; @users } format.json { render :json =&gt; @users } format.js end end </code></pre> <p>Thanks for any ideas.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USViktor Trón
    1. USAndy Harvey
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POHow to render two paginated and ajaxable collections in the same view?
      1. USAndy Harvey
      1. VTBountyStart
    2. VO
      singulars
      1. POHow to render two paginated and ajaxable collections in the same view?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POHow to render two paginated and ajaxable collections in the same view?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COwhen you say that the pagination isn't working, what happens?
      singulars
      1. POHow to render two paginated and ajaxable collections in the same view?
      1. USFrederick Cheung
    2. COnothing! I have a javascript function making the ajax request. The function runs (it adds a spinner.gif) but nothing else happens. Do you need a log? This issue seems strange to me. Everything works fine with `@user` but falls apart when I try to pass as a local. Is there any reason why will_paginate would not accept a local?
      singulars
      1. POHow to render two paginated and ajaxable collections in the same view?
      1. USAndy Harvey
    3. COWhy aren't you passing any locals when you do escape_javascript(render("users/user")) ?
      singulars
      1. POHow to render two paginated and ajaxable collections in the same view?
      1. USFrederick Cheung
 

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