StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20079575
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-11-19T18:47:18.880
FavoriteCount
0
LastActivityDate
2013-11-19T18:47:18.880
LastEditDate
LastEditorUserId
0
OwnerUserId
2209525
ParentId
20077652
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
<p>This is easy to get confused on, so lets look at what's happening. The sidebar code is:</p> <p><a href="https://github.com/spree/spree/blob/2d31d8a69d66e2555e00f67e3227a54a531aa6b8/frontend/app/views/spree/shared/_sidebar.html.erb" rel="nofollow">https://github.com/spree/spree/blob/2d31d8a69d66e2555e00f67e3227a54a531aa6b8/frontend/app/views/spree/shared/_sidebar.html.erb</a></p> <pre><code><aside id="sidebar" class="columns four" data-hook> <%= yield :sidebar %> </aside> </code></pre> <p><a href="https://github.com/spree/spree/blob/v2.1.2/frontend/app/views/spree/home/index.html.erb" rel="nofollow">https://github.com/spree/spree/blob/v2.1.2/frontend/app/views/spree/home/index.html.erb</a></p> <pre><code><% content_for :sidebar do %> <div data-hook="homepage_sidebar_navigation"> <%= render :partial => 'spree/shared/taxonomies' %> </div> <% end %> <div data-hook="homepage_products"> <%= render :partial => 'spree/shared/products', :locals => { :products => @products } %> </div> </code></pre> <p>When this is evaluated, the stuff <strong>within</strong> <code>content_for :sidebar</code> will replace <code>yield :sidebar</code></p> <p>Your problem is that when you're doing insert_before. You get this:</p> <pre><code><h1>Hola</h1> <% content_for :sidebar do %>  <% end %> <div data-hook="homepage_products">...</div> </code></pre> <p>The content_for can occur at any point in this file, it doesn't really matter since it's just saying what goes in the yield. So in the output, it will come before the homepage_products div, which is what you get in your output.</p> <p>Insert_after does the following:</p> <pre><code><% content_for :sidebar do %> <h1>Hola</h1>  <% end %> <div data-hook="homepage_products">...</div> </code></pre> <p>So I'd expect that to appear within the section that's being yielded. Something like this:</p> <pre><code><aside id="sidebar" class="columns four" data-hook> <h1>Hola</h1>  </aside> </code></pre> <p>Which is also what you see.</p> <p>If you want something to appear before the sidebar, as in your example, you should do a different override. You should override <code>spree/shared/_sidebar</code> and insert_before <code>#sidebar</code>.</p> <p>Hope that clears things up.</p>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PODeface in spree home index
  singulars
  PostTypePostTypeId
  PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USgmacdougall
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. PODeface in spree home index
  singulars
  PostTypePostTypeId
  PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
  singulars
  PostPostId
  PO
  UserUserId
  This table or related slice is empty.
  VoteTypeVoteTypeId
  VTAcceptedByOriginator
2. VO
  singulars
  PostPostId
  PO
  UserUserId
  This table or related slice is empty.
  VoteTypeVoteTypeId
  VTUpMod
CommentsPostId
1. COAmazing, thank you so much !!
  singulars
  PostPostId
  PO
  UserUserId
  USGhar

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.