Thread

I’m having an issue where entries entered with a future date/time are not rolling live when the entry date/time comes. I’ve checked the localization settings for the CP and for the user (both are set to the same, correct time zone). I can only force the entries live by returning to the entry, clicking the entry_date to the current time/date, and submitting. Any manually set future date is not pushing live. Note, caching is off and we have waited as long as several hours to see if they would post correctly. Am I missing an obvious setting?

Further testing shows that the individual entry is visible when it hits the entry_date time; however it does not show in the landing page for the section (has the 8 most-recent entries). Here is the code for the channel:entries tag:

{exp:channel:entries channel="color_palettes" limit="8" orderby="date" sort="desc" paginate="bottom" show_future_entries="no"}

Again, oddly, to get the post to show, all I have to do is go into the entry and resubmit.

Hi Shanan,

Could you show the opening tag you’re using for the single entry pages as well so that we may compare? I’m not seeing anything obvious that would be the solution here, so looking at the code you’re using for the single entry page would help.

Also, what version EE are you running?

Opening tag for single entries:

{exp:channel:entries channel="color_palettes" dynamic="yes" limit="1"}

Version number for ExpressionEngine:
v2.3.1 - Build: date 20111017

While you said you had caching off, it actually sounds like caching may be enabled somewhere. The reason I say that is because submitting a channel entry will clear the cache, and its the only thing that makes sense for why a live entry wouldn’t show up on a particular template.

So the next time it happens, before you do anything else, clear your cache. Do the entries now show where they are supposed to? If so, then it was the cache indeed. At that point, you’ll want to then investigate the different levels of caching with EE to see where it might be enabled.

Thank you. Dynamic query caching was in fact enabled. Disabling it fixed the problem.

Question: as I look to tweak the performance on the site, will regular Query caching and/or template caching allow for future entries to post as they pass their entry dates? Is dynamic query caching the only cache method that is not recommended for this instance? Tag-level caching seems to work just fine, for example.

Likewise, is there additional documentation on dynamic query caching beyond the short description here? http://ellislab.com/expressionengine/user-guide/general/caching.html
I would like to dig deeper into what it is doing specifically so I can better determine which cache method works best for which situations.

Glad to hear that fixed it up! That’s the only documentation we’ve got on caching, and while those are the only EE-specific caching methods available, that doesn’t mean those are the only caching methods at your disposal. You can still employ caching at the web server, database server, or PHP level as well, so you may want to work with your host to examine those possibilities.

Tag caching and template caching allow you to set a “time to live” for each cache by using the refresh parameter, so you can use those caches and be sure that, at the most, your content is never out of date for very long.