Good afternoon, there is Views that displays rarely updated information, but with a large number of different CSS classes and HTML tags, in order not to load the database and the Views module itself once again, I thought it would be the most ideal to put all the output in the cache (i.e. already generated HTML)
For this, in the additional settings in the Caching section, I activated the Rendered output - 6 hours.
However, when displaying the Display query log in the Devel module, I noticed that the system does not access this cache in cache_views_data, i.e. it was formed in the database by a record with ready-made HTML code, and Views does not use it.
If I choose caching of the Query results type, then it is successfully accessed and used
Maybe I don't fully understand the principle of operation of this caching, and it seems to me that the choice should be only between two options without the possibility of choosing both, i.e. either it caches the result of the query, and then wraps it in all sorts of styles, or it caches everything completely, and Views remains only for the user to output it with minimal load
Thanks!
Comments