I recently had a client referred to me who has an existing EE build, v2.73, and some of their entries just stopped displaying on their templates. According to them, no code has changed and no software (EE or add ons) have been updated.

I created a blank template to put a simple channel loop in to try some of the common problems; dynamic="no", making sure all statuses are accounted for, show_expired, show_future_entries. None of it worked. Some entries' channel data would display, and others wouldn't. All entries, even the one's not displaying, are visible in the backend and I can see them in the database.

So I decided to see if I could pull out the data with the exp:query tag, and sure enough I can. I can pull the data of an entry with the exp:query tag, but not the same entry's data with an exp:channel:entries tag.

I've never encountered this before and have no idea how to troubleshoot it. Thought I'd see if anyone had any ideas.

The code below is on an otherwise blank template. The {article_text} field is mapped to field_id_3 in the exp_channel_data table.

{exp:channel:entries entry_id="3208" dynamic="no"}

      Channel Tag:<br/>


{exp:query sql="SELECT field_id_3 FROM exp_channel_data WHERE entry_id = '3208' "}

      Query Module<br/>


Both tags in the above block output content when I changed the entry_id to an article that is working on the front end. I'm straight up baffled. Any suggestions would be greatly appreciated.

  • I'd wager there is an extension/module throwing hidden errors. Turn profiler on or temporarily disable extensions. Commented Jan 20, 2017 at 3:14
  • Yeah, I'm digging through the profiler output now to see what I can see. Thanks.
    – hypind
    Commented Jan 21, 2017 at 2:40

2 Answers 2


If that entry does not have the status of "Open", Make sure you set the status parameter to include what ever that entry has. i. e. status="Open|Draft|Review" The channel entries tag defaults to Open entries only. The Query Module is ignoring status unless you explicitly set it in the where clause.

  • Thanks for the response. Both entries have a status of open, so unfortunately that's not what's going on.
    – hypind
    Commented Jan 21, 2017 at 2:40

Looks like this was unrelated to native EE. After some investigation the problem seems to be with an add-on.

  • Most likely your host has upgraded PHP to a newer version that is incompatible with a module. Commented Jan 21, 2017 at 9:25
  • I consulted the host, they're still running PHP v5.3.10, Ubuntu 12.04LTS. So no updates to the environment for quite some time. Client just decided to disable the add-on at this point. Thanks though.
    – hypind
    Commented Jan 23, 2017 at 21:52

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.