We faced a weird issue with status="Featured" for our channel entry tag today, when we changed the custom status of our health topic channel entry from "Featured" to "Closed", and created a new health topic channel entry with the status="Featured". This process has worked in the past, but doesn't seem to work today.

The tag looks like this:

{exp:channel:entries channel="health_topics" limit="1" status="Featured" dynamic="no"}
//HTML code

Nothing is displayed is the sections with the above snippet. This issue is common to another channel "Event".

What could be the issue? Any assistance is much appreciated. Thanks in advance!

  • 1
    Have you checked the date of the entry? Is it on future?
    – Sobral
    Apr 21, 2015 at 19:29
  • Yes, I have checked the date of entry, and it is not set to a future date. Apr 22, 2015 at 18:55
  • Are you using any sort of caching mechanisms? EE has tag caching and template caching, or there could be some upstream caches like memcache or APC?
    – Blatant
    May 22, 2015 at 8:55

2 Answers 2


First things first, have you double checked your Status Group assignment in Channel Groups?

Admin -> Channel Administration -> Channels -> Edit Group Assignments

Sorry if you have checked this, you don't mention anything about your Status group setup and it's always good to start at the start!

  • Yes, I have checked the status group assignment. No issues with that. Apr 22, 2015 at 18:56
  • Have you resaved the entries? What happens if u use status="NOT featured' ? May 22, 2015 at 4:14

I found the solution to the problem. The problem is actually due to caching. Turned off 'Cache Dynamic Channel Queries' in the global channel preferences and now the results are coming up. I did try clearing all cache before I did that and it made no difference, so I believe there was a problem with file/folder permissions. It's similar to the error when we try to write to the cache folder and I noticed a similar error saving templates (when it tries to save templates to files). There was a cache file for that URL, EE couldn't clear the cache file, so it kept being used to figure if there were any matching results and coming back 'no'. Thanks everyone for your suggestions!

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.