mirror of
https://github.com/silverstripe/silverstripe-framework
synced 2024-06-29 07:59:31 +02:00
e632ee3e52
- create a new documentation section explaining the "cached" block - clean up the Performance documentation section, moving explanations about "cached" block away, adding new warnings and recommendations
961 B
961 B
| title | summary | icon |
|---|---|---|
| Caching | How template variables are cached. | rocket |
Caching
Object caching
All functions that provide data to templates must have no side effects, as the value is cached after first access. For example, this controller method will not behave as you might imagine.
private $counter = 0;
public function Counter()
{
$this->counter += 1;
return $this->counter;
}
$Counter, $Counter, $Counter
// returns 1, 1, 1
When we render $Counter to the template we would expect the value to increase and output 1, 2, 3. However, as
$Counter is cached at the first access, the value of 1 is saved.
Partial caching
Partial caching is a feature that allows caching of a portion of a page as a single string value. For more details read its own documentation.
Example:
<% cached $CacheKey if $CacheCondition %>
$CacheableContent
<% end_cached %>