Post-process any rendered data.
This can be valuable to be able to cache a view and still have some level of dynamic output. In an ideal world, the actual output will include HTML comment-based tokens, and then the post process can replace those tokens. This hook can be utilized by themes.
Example usage. If it is known that the view is a node view and that the primary field will be a nid, you can do something like this: @code <!--post-FIELD-NID--> @encode And then in the post-render, create an array with the text that should go there: @code strtr($output, array('<!--post-FIELD-1-->' => 'output for FIELD of nid 1'); @encode All of the cached result data will be available in $view->result, as well, so all ids used in the query should be discoverable.
\Drupal\views\ViewExecutable $view: The view object about to be processed.
string $output: A flat string with the rendered output of the view.
CacheBackendInterface $cache: The cache settings.
Note: this list is generated by pattern matching, so it may include some functions that are not actually implementations of this hook.
function hook_views_post_render(ViewExecutable &$view, &$output, CacheBackendInterface &$cache) {
// When using full pager, disable any time-based caching if there are fewer
// than 10 results.
if ($view->pager instanceof Drupal\views\Plugin\views\pager\Full && $cache instanceof Drupal\views\Plugin\views\cache\Time && count($view->result) < 10) {
$cache->options['results_lifespan'] = 0;
$cache->options['output_lifespan'] = 0;
}
}