Project

General

Profile

Actions

Bug #90406

closed

Caching of pages is not adjusted for content with "Publish Date" / "Expiration Date" (starttime, endtime)

Added by Sybille Peters about 4 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Caching
Target version:
-
Start date:
2020-02-17
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
9
PHP Version:
Tags:
cache expiration starttime endtime
Complexity:
Is Regression:
Sprint Focus:

Description

Content with a "Publish date" or "Expiration Date" is not rendered correctly because of caching of page (content).

If the content has a "Publish date" that intersects with the cache duration, I would expect the cache duration to be adjusted (this one time).

Example:

Time of created content: Feb 17, 2020 - 14:00
Cache duration: 24 h (until Feb 18, 2020 - 14:00)
Publish time: Feb 17, 2020 - 14:05 - infinite

In this case, the content is not published until Feb 18 14:00 but it should be published Feb 17 14:05.

I would expect the cache duration to be adjusted accordingly, or maybe a warning to be issued.

For pages with a publish date, this would also influence the menu (of other pages), so I guess it is not so easy to get this right entirely.

Reproduce

  1. Create a page with a content element which should be published some time in the future (the time interval being less than current cache period)
  2. Render page (so cache is filled)
  3. Wait until "Publish date" passed and load page again

Actual result

The content with a "Publish date" is not displayed after the "publish date". The cache of the page must be flushed for it to be rendered.

Expected result

When reloading the page after the publish date came, the content should be displayed

Actions

Also available in: Atom PDF