hook_views_post_render

hook_views_post_render(ViewExecutable $view, &$output, CachePluginBase $cache)

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 used 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:

And then in the post-render, create an array with the text that should go there:

  strtr($output, array('<!--post-FIELD-1-->' => 'output for FIELD of nid 1');

All of the cached result data will be available in $view->result, as well, so all ids used in the query should be discoverable.

Parameters

\Drupal\views\ViewExecutable $view: The view object about to be processed.

string $output: A flat string with the rendered output of the view.

\Drupal\views\Plugin\views\cache\CachePluginBase $cache: The cache settings.

See also

\Drupal\views\ViewExecutable

Related topics

Hooks

Define functions that alter the behavior of Drupal core.

File

core/modules/views/views.api.php, line 854

Describes hooks and plugins provided by the Views module.

Code

function hook_views_post_render(ViewExecutable $view, &$output, CachePluginBase $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;
  }
}