<p>If the entry is in a subdirectory, the image path will be incorrect. If the images are in a folder called &quot;assets&quot; in your home folder:</p>
<p>image.url for your main page would be &quot;assets/imagename.jpg&quot;</p>
<p>image.url for your entries in &quot;blog&quot; SHOULD be &quot;../assets/imagename.jpg&quot; BUT it will still return just &quot;assets/imagename.jpg&quot; instead of jumping up a directory to get the assets directory. Therefore, no image found at blog/assets/imagename.jpg.</p>
<p>Depending on your setup you might try <code>img src=&quot;{{ siteUrl }}/{{ image.url }}&quot;</code>. This will fetch the full site path to the image every time no matter what where it's called from.</p>

CC BY-SA 4.0
2021-02-12T01:32:16.323Z
2021-02-12T01:32:16.323Z
Wonko
<p>When templating my Craft site, I have run into an issue with on both my Local &amp; Server environments on the latest version of Craft. I am running a LAMP stack and I think I have been able to narrow down the issue to being a file directory issue or section config mistake.</p>
<p>My Blog/Index page functions perfectly and will include all asset fields without issue, yet when I click on a blog post to navigate to a blog/_entry, all assets stop functioning. Below is the twig code that I use. I have only one volume titled &quot;images&quot; sitting within the web/ folder.</p>
<p><a href="https://i.sstatic.net/K4RdL.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/K4RdL.png" alt="enter image description here" /></a></p>
<pre><code>{% for image in entry.featureImage %}
  &lt;img src=&quot;{{ image.url }}&quot; alt=&quot;{{ image.title }}&quot; data-holder-rendered=&quot;true&quot;/&gt;
{% endfor %}
</code></pre>
<p>So the funky thing is that the {{ image.title }} entry seems to work perfectly and will call the image, but will not display it. Maybe this could be an issue with file organization? The same problem occurs with my global assets (logos).</p>
<p>Here's a screenshot of what this looks like in action.</p>
<p>Any direction is much appreciated! New to development &amp; not the brightest crayon in the shed so I'm having difficulty  figuring out how to approach this problem, although I didn't seem to locate any issues among the config/ files.</p>

<craft3>
Blog/_entry breaking all assets globals like header & footer logos
# Blog/_entry breaking all assets globals like header & footer logos

(Asked by: username_0 on 2021-02-10)

When templating my Craft site, I have run into an issue with on both my Local & Server environments on the latest version of Craft. I am running a LAMP stack and I think I have been able to narrow down the issue to being a file directory issue or section config mistake.
My Blog/Index page functions perfectly and will include all asset fields without issue, yet when I click on a blog post to navigate to a blog/_entry, all assets stop functioning. Below is the twig code that I use. I have only one volume titled "images" sitting within the web/ folder.

{% for image in entry.featureImage %}
  
{% endfor %}

So the funky thing is that the {{ image.title }} entry seems to work perfectly and will call the image, but will not display it. Maybe this could be an issue with file organization? The same problem occurs with my global assets (logos).
Here's a screenshot of what this looks like in action.
Any direction is much appreciated! New to development & not the brightest crayon in the shed so I'm having difficulty  figuring out how to approach this problem, although I didn't seem to locate any issues among the config/ files.

**Tags:** craft3

---

## 1 answers

### Answer by username_1 on 2021-02-12. Score: 1

If the entry is in a subdirectory, the image path will be incorrect. If the images are in a folder called "assets" in your home folder:

image.url for your main page would be "assets/imagename.jpg"

image.url for your entries in "blog" SHOULD be "../assets/imagename.jpg" BUT it will still return just "assets/imagename.jpg" instead of jumping up a directory to get the assets directory. Therefore, no image found at blog/assets/imagename.jpg.

Depending on your setup you might try `img src="{{ siteUrl }}/{{ image.url }}"`. This will fetch the full site path to the image every time no matter what where it's called from.


---

