In the config array, you can set a new key "cache" to set some caching options.
Below you will see each of these caching options explained. I'd also like to refer to the original concrete5 documentation for the Block Type PHP Controller.
Defaults to true. When block caching is enabled, this means that the block's database record data will also be cached. This can almost always be set to true.
Defaults to false. This determines whether a block will cache its output on POST. Some blocks can cache their output but must serve uncached output on POST in order to show error messages, etc…
Defaults to false. Determines whether a block that can cache its output will continue to cache its output even if the current user viewing it is logged in.
Defaults to false. When block caching is enabled, enabling this boolean means that the output of the block will be saved and delivered without rendering the view() function or hitting the database at all.
Defaults to no time limit (0). When block caching is enabled and output caching is enabled for a block, this is the value in seconds that the cache will last before being refreshed.
Use, by you or one client, in a single end product. The total price includes the item price and a buyer fee.
Use, by you or a client, in 5 single end products. The total price includes the item price and a buyer fee.
Use, by you or a client, in x/xx single end products.
Upon request, quote will be made and sent to you via email.
Got something to say? Need help?View support forum