Bug #27227: Use Runtime Cache in tslib_fe::get_cache_timeout - Core - TYPO3 Forge

Core Indexed Search Linkvalidator Release Cycles Team Resources Workspaces & Versioning TYPO3 CMS Usability Team Community Extensions Distributions Feature-Requests TYPO3 6.2 Projects (+)(Archived Projects)

Bug #27227

Bug #20473: Starttime/endtime is not taken into account when caching

Use Runtime Cache in tslib_fe::get_cache_timeout

Added by Steffen Gebert about 4 years ago. Updated about 2 years ago.

Status:

Closed

Start date:

2011-06-05

Priority:

Should have

Due date:

Assigned To:

% Done:

100%

Category:

Spent time:

Target version:

TYPO3 Version:

4.6

Is Regression:

PHP Version:

Sprint Focus:

Complexity:

Description

Thanks to #20473, start and stop times of records are now taken into account during a page's cache lifetime calculation.
To prevent repeated computations, the value is cached inside tslib_fe::get_cache_timeout, using a class variable getCacheTimeoutCache.

The Runtime Cache (#27208) not only offers a cleaner way to do so, it also provides a remedy against the currently existing problem that get_cache_timeout() does its job exactly twice: Once during menu generation (which seems to work with a cloned copy of TSFE) and once before putting the page contents into the cache. As both class instances share the runtime cache, the second calculation can be safed.

Related issues

Associated revisions

Revision fea7f6ec
Added by Steffen Gebert about 4 years ago

[BUGFIX] Use runtime cache in tslib_fe::get_cache_timeout

Thanks to #20473, start and stop times of records are now taken into
account during a page's cache lifetime calculation.
To prevent repeated computations, the value is cached inside
tslib_fe::get_cache_timeout(), using a class variable
getCacheTimeoutCache.

The Runtime Cache (#27208) not only offers a cleaner way to do so, it
also provides a remedy against the currently existing problem that
get_cache_timeout() does its job exactly twice: Once during menu
generation (which seems to work with a cloned copy of TSFE) and once
before putting the page contents into the cache. As both class instances
share the runtime cache, the second calculation can be safed.

Change-Id: I0b241749639a678ba6c1addd8d57e2256cf52bc2
Resolves: #27227
Depends: #27208
Reviewed-on: http://review.typo3.org/2531
Reviewed-by: Christian Kuhn
Tested-by: Christian Kuhn
Reviewed-by: Philipp Gampe
Tested-by: Philipp Gampe
Reviewed-by: Susanne Moog
Tested-by: Susanne Moog