Also whole caching subsystem is implemented for two reasons – speed and server load (both processing and bandwidth load). There are several types of caching involved in server-client interactions:
=== TABULKA ===This type of cache is implemented everywhere the image is processed via imageGenerator class.
ImageGenerator class
This class is placed in <approot>\class\class_imagegenerator.php
Class is using this methods:
getSrc
This class is used for caching images. When image from Media-library is used in page (anywhere in system, both admin and site – depending on used template) then following procedure is applied:
Image cache directory / path
Both values are defined in config.php.
Default value is: tmp\cache\images
Cached file name format options
This format is defined in cfg.ini.php in section System in variable image_cache_format.
Format can consists from following parts:
Default format is info_hash.ext
Example of file name of cached image
150_150__4f3b0172bb9866239cbf9ba1a3d5c23543a01518.jpg
Example of syntax of using imagegenerator in templates:
ImageGenerator::loadSrc(security::image_getFullPath($value['image_path'] . $value['image_filename']), 180, 220, true, true, true);
For more examples see code_examples.tpl.php.
This type of cache is implemented everywhere the localization string is processed via Lang class.
Cache folder is located in system files repository: /tmp/cache/localization_strings/
Turn on zlib.output_compression for example on your server.
Also the compression should be set for various possible mimetypes: