<p>Okay, solved. </p>

<p>Was an idiot and wasn't using the right tag to output the results of the query. </p>

<p>Sorry and thanks!</p>

CC BY-SA 3.0
2015-09-24T13:10:58.687Z
Glad you got it sorted out, Cole! Can you choose this as the answer so the question will be closed?
Aaron Berkowitz
CC BY-SA 3.0
2015-09-24T16:50:41.933Z
Can you post the tag you used to get things working for folks finding this post in the future?
Anna_MediaGirl
CC BY-SA 3.0
2015-09-24T10:55:20.100Z
2015-09-24T10:55:20.100Z
Cole Henley
<p>How about</p>

<p><code>{% set entry = craft.entries.sectionId(productsAndMarketsLandingPage.id).first() %}</code></p>

CC BY-SA 3.0
2015-09-24T10:18:21.427Z
Sadly still returning empty. We are using locales on the site (with English defaulting to root) - not sure if that is what is causing the problems
Cole Henley
CC BY-SA 3.0
2015-09-24T10:07:46.820Z
2015-09-24T10:07:46.820Z
Steven Grant
<p>I've got a product section on a website where individual product entries are categorised. On the section landing page all the products are listed organised by category. On the individual category pages only the product entries relevant to that category are shown.</p>

<p>The issue I’m having is that for the category landing page I want to pull in the Section landing page content. However when I try the following:</p>

<pre><code>{% set entry = craft.entries.section(‘productsAndMarketsLandingPage’).first() %}
</code></pre>

<p><code>{entry}</code> returns empty. Any thoughts why this isn’t being pulled into this particular page/template? I can access it just fine from within the </p>

<p>The section, template and URL structure is as follows:</p>

<pre><code>Section landing page
url: /products-and-markets
template: /products-and-markets/index
section: productsAndMarketsLandingPage

Category landing page
url: /products-and-markets/{slug}
template: /products-and-markets/_category
section: productsAndMarkets

Product entry page
url: /products-and-markets/{slug}
template: /products-and-markets/_entry
section: productsAndMarkets
</code></pre>

<p>Cheers in advance,</p>

<p>Cole</p>

<templating><entries><categories><url>
Issue accessing single entry from within category template
# Issue accessing single entry from within category template

(Asked by: username_0 on 2015-09-24)

I've got a product section on a website where individual product entries are categorised. On the section landing page all the products are listed organised by category. On the individual category pages only the product entries relevant to that category are shown.
The issue I’m having is that for the category landing page I want to pull in the Section landing page content. However when I try the following:
{% set entry = craft.entries.section(‘productsAndMarketsLandingPage’).first() %}

{entry} returns empty. Any thoughts why this isn’t being pulled into this particular page/template? I can access it just fine from within the 
The section, template and URL structure is as follows:
Section landing page
url: /products-and-markets
template: /products-and-markets/index
section: productsAndMarketsLandingPage

Category landing page
url: /products-and-markets/{slug}
template: /products-and-markets/_category
section: productsAndMarkets

Product entry page
url: /products-and-markets/{slug}
template: /products-and-markets/_entry
section: productsAndMarkets

Cheers in advance,
Cole

**Tags:** templating, entries, categories, url


---

## 2 answers

### Answer by username_0 on 2015-09-24. Score: 1 | Accepted answer

Okay, solved.

Was an idiot and wasn't using the right tag to output the results of the query.

Sorry and thanks!

> **Comments:**
> **username_1**: Glad you got it sorted out, Cole! Can you choose this as the answer so the question will be closed?  
> **username_2**: Can you post the tag you used to get things working for folks finding this post in the future?  

---

### Answer by username_3 on 2015-09-24. Score: 0

How about

`{% set entry = craft.entries.sectionId(productsAndMarketsLandingPage.id).first() %}`

> **Comments:**
> **username_0**: Sadly still returning empty. We are using locales on the site (with English defaulting to root) - not sure if that is what is causing the problems  

---

