0a669704ea
- Smarty 4.1.1 → 4.5.6 (behebt dynamic property deprecations) - Core-Klassen: #[\AllowDynamicProperties] für Admin_role, base, Config, Customer, Customer_group, CustomerGroups, Item, Structure, website - website.class.php: counts[parent_id] initialisieren vor ++ (PHP 8.1) - layout.class.php: HTTP_ACCEPT_LANGUAGE mit isset-Guard - website_init.php: session_status()-Check vor session_start - .htaccess: HTTPS-Redirect via X-Forwarded-Proto (statt SERVER_PORT) - themes/easyshop_advanced/media/: Parent-Theme-Assets nachgezogen - .gitignore: smarty.4.1.1.bak ausschließen
25 lines
1.2 KiB
Markdown
25 lines
1.2 KiB
Markdown
Caching
|
|
=======
|
|
|
|
Caching is used to speed up a call to [`display()`](./api-functions/api-display.md) or
|
|
[`fetch()`](./api-functions/api-fetch.md) by saving its output to a file. If a cached
|
|
version of the call is available, that is displayed instead of
|
|
regenerating the output. Caching can speed things up tremendously,
|
|
especially templates with longer computation times. Since the output of
|
|
[`display()`](./api-functions/api-display.md) or [`fetch()`](./api-functions/api-fetch.md) is cached, one
|
|
cache file could conceivably be made up of several template files,
|
|
config files, etc.
|
|
|
|
Since templates are dynamic, it is important to be careful what you are
|
|
caching and for how long. For instance, if you are displaying the front
|
|
page of your website that does not change its content very often, it
|
|
might work well to cache this page for an hour or more. On the other
|
|
hand, if you are displaying a page with a timetable containing new
|
|
information by the minute, it would not make sense to cache this page.
|
|
|
|
## Table of contents
|
|
- [Setting Up Caching](./caching/caching-setting-up.md)
|
|
- [Multiple Caches Per Page](./caching/caching-multiple-caches.md)
|
|
- [Controlling Cacheability of Output](./caching/caching-groups.md)
|
|
- [Custom Cache Implementation](./caching/caching-custom.md)
|