Bug #23180
Starttime/endtime for pages and content is not taken into account when caching
| Status: | Rejected | Start date: | 2010-07-14 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assigned To: | - | % Done: | 0% |
|
| Category: | - | Spent time: | - | |
| Target version: | - | |||
| TYPO3 Version: | 4.3 | Is Regression: | ||
| PHP Version: | 5.2 | Sprint Focus: | ||
| Complexity: |
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)
15116.diff
(7.7 kB)
Related issues
History
#1 Updated by Stefan Neufeind about 4 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.
#2 Updated by Xavier Perseguers about 4 years ago
- Category deleted (
Communication) - Target version changed from 4.6.0-beta1 to 4.6.0-beta2
#3 Updated by Steffen Gebert almost 4 years ago
- Assigned To deleted (
Dmitry Dulepov) - Target version deleted (
4.6.0-beta2)
I'd say that's fixed with 4.6
#4 Updated by Steffen Gebert almost 4 years ago
- Status changed from Accepted to Rejected