-
Notifications
You must be signed in to change notification settings - Fork 127
entry date / expiration date not working properly #4584
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@jelle-burodeng what's the opening Also to make sure, the entry status is "open" but with entry date in the future? And you need to re-save the entry in order for it to show up? As well, is there any caching involved? |
it's an embed:
the entry status is "open" but with entry date in the future? Yes. |
Any word on this @intoeetive ? |
@jelle-burodeng - sorry, somehow this came out of my radar. So I see in your code that you have caching set to 10 hours. If the cache for the page was re-build close before the date when entry was supposed to go live (or expire) it will still be shown up for almost 10 hours - until the next cache rebuild. Updating the entry clears the cache, but if you don't touch the database - the system will just serve whatever it has cached So if you need the entries to go live/expire at exact time, you need to no cache at all, use smaller caching period or clear the caches at desired time |
We are experiencing an issue with the entry date. Our editors write articles, and set an entry date in the future for the article to go online. This was working just fine, untill we updated the site to 7.4.11.
We have to manually change the status to open. On another site (same EE version) we recently had the same issue the other way around, where the expiration date didn't get respected
The text was updated successfully, but these errors were encountered: