I upgraded to Assets 2.1 yesterday and am experiencing a problem when a non-required Assets 2.1 field in a Matrix row is empty. On a single-entry template (limit=“1” and require_entry=“yes” parameters in my exp:channel:entries tag) this situation is causing the {if no_results} conditional to be invoked. Selecting a file for the empty, non-required, Assets field and re-saving the entry fixes the problem.

Thanks in advance for your help.

Matrix 2.5.3 ExpressionEngine 2.5.2 Build 20120606

Here is template code that will trigger the issue:

{exp:channel:entries channel="videos" limit="1" status="open" disable="categories|category_fields|pagination|member_data" require_entry="yes"}{if no_results}{redirect="404"}{/if}<!doctype html>
<html lang="en">
<title>Page Title</title>


{sidebar_videos limit="1"}

<iframe src="//www.youtube.com/embed/{youtube_video_id}"></iframe>


<h3>All Videos</h3>

<ul id="videothumbs">


<li><a href="/features/videos/{entry_id}/{row_id}" title="{youtube_title}”>{youtube_thumbnail}<img src="{url}" alt="{alt_text}">{/youtube_thumbnail}</a></li>




{sidebar_videos} is my Matrix field, which is not required. {youtube_thumbnail} is the problem Assets field within the Matrix field. The other columns in the Matrix field are:

{youtube_title} (Text/required)

{youtube_video_id} (Text/required)

{youtube_caption} (Wygwam/required)

{youtube_thumbnail} (Assets/not required)

  • Hey jauses - can you post your full template code? I'd like to test this and want to make sure I'm recreating what you've done. Thank you!
    – Lisa
    Commented Apr 10, 2013 at 19:50
  • Updated my real answer with the fix for you. :)
    – Lisa
    Commented Apr 12, 2013 at 17:41

1 Answer 1


Edit again! jauses - can you try changing line 1324 in ft.assets.php file from

if (! $data)


if (! $data && $this->var_id)

? That should fix this up for you.

Thank you!

  • I can replicate that problem, too. It’s actually failing even if I limit the output to a single entry that has a populated Assets field. The required_entry parameter seems to be the problem child here. Removing it fixes the problem, although then, of course, the {if no_results} conditional fails.
    – jauses
    Commented Apr 11, 2013 at 17:55
  • Yep, it's an interesting one - I have submitted it as a bug for 2.1 Thank you jauses!
    – Lisa
    Commented Apr 11, 2013 at 20:10
  • Boom! That did the trick. Thanks so much!
    – jauses
    Commented Apr 13, 2013 at 19:15
  • My pleasure, jauses!
    – Lisa
    Commented Apr 15, 2013 at 15:38

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.