Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The best strategy would be to move what's in your snippet into a separate template file while you try to figure this out. I noticed a couple of things that seem off to me in your sidebar snippet code. </p> <pre><code>&lt;div id="ebook_offer"&gt; {exp:channel:entries channel="test"} &lt;h3&gt;Ebook&lt;/h3&gt; {/exp:channel:entries} &lt;/div&gt; &lt;div id="about_blog"&gt; {exp:channel:entries channel="blog_sidebar"} &lt;h3&gt;About Obsia's Blog&lt;/h3&gt; {/exp:channel:entries} &lt;/div&gt; </code></pre> <p>This doesn't really seem the right way to use the {exp:channel:entries} tag. You mentioned "ebook_offer" was a channel field. But here you're using it as a static id for an HTML div. If "ebook_offer" is a field I would expect something like this:</p> <pre><code>&lt;h3&gt;Ebook&lt;/h3&gt; {exp:channel:entries channel="test"} {ebook_offer} {/exp:channel:entries} </code></pre> <p>Same with "about_blog"</p> <pre><code>&lt;h3&gt;About Obsia's Blog&lt;/h3&gt; {exp:channel:entries channel="blog_sidebar"} {about_blog} {/exp:channel:entries} </code></pre> <p>Also I noticed you said the channel was named "sidebar" but in your {exp:channel:entries} tag you're using "blog_sidebar". Which isn't the same thing, is your channel's shortcode "sidebar" or "blog_sidebar"?</p> <p>Finally this is a little off to me</p> <pre><code>&lt;div id="demo" dynamic="no" limit="1"&gt; &lt;/div&gt; </code></pre> <p>"dynamic" and "limit" only work on ExpressionEngine {exp:channel:entries} tags, not regular HTML elements (like DIVs). I would try using Bitmanic and Peter's suggestion again, but apply it to {exp:channel:entries} like so:</p> <pre><code>{exp:channel:entries channel="blog_sidebar" dynamic="off"} ... {/exp:channel:entries} </code></pre> <p>If you're new to ExpressionEngine I highly recommend videos &amp; tutorials by Ryan Ireland <a href="http://eeinsider.com/videos" rel="nofollow">http://eeinsider.com/videos</a></p>
    singulars
    1. This table or related slice is empty.
    1. POexpression engine: Content in channel fields don't show up on the webpage when called in a template
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USPatrick Pohler
    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. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COMade the corrections - some of them were due to oversight. Problem is it still does not work but it works if I replace channel = "blog_sidebar" with "blog". In short it does display content from blog channels but not blog_sidebar channels - any clue?
      singulars
      1. PO
      1. USstrangeloops
    2. COIn that case, I would imagine that your issue has to do with how you set up the blog_sidebar channel. I can't think of any particular settings that would stop your channel entries from displaying on a page, unfortunately.Are you sure you've been saving entries to the blog_sidebar channel?
      singulars
      1. PO
      1. USRay
    3. COyes I checked that - that was my conclusion but not sure what the problem is. Thank you Patrick, Bitmanic and Peter.
      singulars
      1. PO
      1. USstrangeloops
 

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