Florian Eisenmenger
41ccc32b5d
|
vor 2 Jahren | |
|---|---|---|
| .. | ||
| Block | vor 2 Jahren | |
| Console/Command | vor 2 Jahren | |
| Controller | vor 2 Jahren | |
| Exception | vor 2 Jahren | |
| Helper | vor 2 Jahren | |
| Model | vor 2 Jahren | |
| Observer | vor 2 Jahren | |
| Plugin | vor 2 Jahren | |
| Test | vor 2 Jahren | |
| ViewModel | vor 2 Jahren | |
| etc | vor 2 Jahren | |
| i18n | vor 2 Jahren | |
| view | vor 2 Jahren | |
| LICENSE.txt | vor 2 Jahren | |
| LICENSE_AFL.txt | vor 2 Jahren | |
| README.md | vor 2 Jahren | |
| composer.json | vor 2 Jahren | |
| registration.php | vor 2 Jahren | |
README.md
The PageCache module provides functionality of caching full pages content in Magento application. An administrator may switch between built-in caching and Varnish caching. Built-in caching is default and ready to use without the need of any external tools.
Requests and responses are managed by PageCache plugin. It loads data from cache and returns a response. If data is not present in cache, it passes the request to Magento and waits for the response. Response is then saved in cache.
Blocks can be set as private blocks by setting the property ‘_isScopePrivate’ to true. These blocks contain personalized information and are not cached in the server. These blocks are being rendered using AJAX call after the page is loaded. Contents are cached in browser instead.
Blocks can also be set as non-cacheable by setting the ‘cacheable’ attribute in layout XML files. For example <block class="Block\Class" name="blockname" cacheable="false" />. Pages containing such blocks are not cached.