Project

General

Profile

Actions

Bug #23180

closed

Starttime/endtime for pages and content is not taken into account when caching

Added by Dmitry Dulepov over 14 years ago. Updated about 13 years ago.

Status:
Rejected
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2010-07-14
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.3
PHP Version:
5.2
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

TYPO3 page cache ignores start and end time for content and pages. This causes problems related to caching:
- if a content element has start time set, it will not be shown at that time until the page expires
- if a content element has end time set, it will be shown after that time until the page expires
- If a page has start time set, it will not be shown at the right time in menu on cached pages until cache for those pages expires
- If a page has end time set, it will be shown in menu on cached pages after the end time causing 404 errors until cache for those pages expires

(issue imported from #M15116)


Files

15116.diff (7.7 KB) 15116.diff Administrator Admin, 2010-07-14 13:43

Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Feature #19283: page cache is not influenced by tt_content.starttime/endtimeClosed2008-09-03

Actions
Related to TYPO3 Core - Bug #20473: Starttime/endtime is not taken into account when cachingClosedSteffen Gebert2011-06-05

Actions
Actions #1

Updated by Stefan Neufeind over 13 years ago

Dmitry, could you please see if this is what #20473 (now resolved; you took part in the discussion over there as well) resolves? It looks like from reading. If so, please close this one.

Actions #2

Updated by Xavier Perseguers over 13 years ago

  • Category deleted (Communication)
  • Target version changed from 4.6.0-beta1 to 4.6.0-beta2
Actions #3

Updated by Steffen Gebert about 13 years ago

  • Assignee deleted (Dmitry Dulepov)
  • Target version deleted (4.6.0-beta2)

I'd say that's fixed with 4.6

Actions #4

Updated by Steffen Gebert about 13 years ago

  • Status changed from Accepted to Rejected
Actions

Also available in: Atom PDF