<p>So a <a href="https://github.com/nystudio107/craft-imageoptimize#using-the-optimized-images-field" rel="nofollow noreferrer">per the documentation</a>, the <strong>Optimized Images</strong> field should <em>only</em> be added to an Asset Volume's layout. You do not need to, and should not add that field to your Section field layouts.</p>

<p>Please verify for me that after doing so, when you double-click on an Asset, you see a display similar to this:</p>

<p><img src="https://raw.githubusercontent.com/nystudio107/craft-imageoptimize/v1/resources/screenshots/image-variant-field.png" alt="Screenshot"></p>

<p>c.f.: <a href="https://github.com/nystudio107/craft-imageoptimize/issues/106" rel="nofollow noreferrer">https://github.com/nystudio107/craft-imageoptimize/issues/106</a></p>

<p><strong>Resolution:</strong> This ended up just being some local config issues with Asset Volumes, and then getting rid of pending stuck Queue jobs. After that, away we go!</p>

CC BY-SA 4.0
2018-09-17T13:29:20.703Z
2018-09-17T15:42:32.490Z
2018-09-17T15:42:32.490Z
andrew.welch
<p>In Craft CMS, I am using the imageoptimize plugin to optimize images. I have added field imageoptimize &amp; in assets created volume added field in field layout but when I am adding entry it showing me the message 'OptimizedImages fields only work when added to an Asset Volume's layout.'.</p>

<p>I am using Craft CMS version 3.024 and ImageOptimize plugin version 1.4.38.
Why is the field not showing up?</p>

CC BY-SA 4.0
2018-09-17T10:42:52.293Z
`"but when i am adding entry"` The field is not supposed to work for entries, it will only work for assets
Robin Schambach
CC BY-SA 4.0
2018-09-17T11:01:23.190Z
@RobinSchambach In front-end, we have to code for that to make it image optimized?
Pramod Pandey
CC BY-SA 4.0
2018-09-17T11:03:28.810Z
For the source sets and sizes yes
Robin Schambach
CC BY-SA 4.0
2018-09-17T11:06:50.697Z
@RobinSchambach In front-end i have tried this code :- {% set optimizedImages = entry.myAssetField.one().optimizedImagesField %}
    <img src="{{ optimizedImages.src() }}"
         srcset="{{ optimizedImages.srcset() }}"
         sizes="100vw" />
It is not showing images.
Pramod Pandey
<plugin-imageoptimize>
Using imageoptimize plugin not showing field on entries
# Using imageoptimize plugin not showing field on entries

(Asked by: username_0 on 2018-09-17)

In Craft CMS, I am using the imageoptimize plugin to optimize images. I have added field imageoptimize & in assets created volume added field in field layout but when I am adding entry it showing me the message 'OptimizedImages fields only work when added to an Asset Volume's layout.'.

I am using Craft CMS version 3.024 and ImageOptimize plugin version 1.4.38.
Why is the field not showing up?

**Tags:** plugin-imageoptimize

> **Comments:**
> **username_1**: `"but when i am adding entry"` The field is not supposed to work for entries, it will only work for assets  
> **username_0**: @RobinSchambach In front-end, we have to code for that to make it image optimized?  
> **username_1**: For the source sets and sizes yes  
> **username_0**: @RobinSchambach In front-end i have tried this code :- {% set optimizedImages = entry.myAssetField.one().optimizedImagesField %}     <img src="{{ optimizedImages.src() }}"          srcset="{{ optimizedImages.srcset() }}"          sizes="100vw" /> It is not showing images.  

---

## 1 answers

### Answer by username_2 on 2018-09-17. Score: 2 | Accepted answer

So a [per the documentation](https://github.com/nystudio107/craft-imageoptimize#using-the-optimized-images-field), the **Optimized Images** field should *only* be added to an Asset Volume's layout. You do not need to, and should not add that field to your Section field layouts.

Please verify for me that after doing so, when you double-click on an Asset, you see a display similar to this:

![Screenshot](https://raw.githubusercontent.com/nystudio107/craft-imageoptimize/v1/resources/screenshots/image-variant-field.png)

c.f.: <https://github.com/nystudio107/craft-imageoptimize/issues/106>

**Resolution:** This ended up just being some local config issues with Asset Volumes, and then getting rid of pending stuck Queue jobs. After that, away we go!


---

