Discovered in 📌 Search must be indexed after recipe is applied Active .
automated_cron runs at the end of request, after the session is closed.
Views can use session storage to set default values of exposed input.
Views can also be search indexed if they're rendered as part of rendering a node (or any search indexing that ends up rendering views).
However, ViewsExecutable happily checks session information when rendering - this could theoretically mean that an individual user's saved filter settings would influence what gets search indexed, which should not happen. Either way, it results in headers already sent with automated cron.
It also looks like ViewsExecutable does this for anonymous users even when the view isn't configured to do so.
e.g. FilterPluginBase checks roles, ViewExecutable doesn't.
At a minimum, ViewExecutable should not be checking the session when the view isn't configured for it.
Active
11.0 🔥
views.module
According to 📌 Search must be indexed after recipe is applied Active this is causing PHP warnings in Drupal CMS, so tagging.
Is this a duplicate of 🐛 Views exposed filter reset creates session for anonymous Active or just similar?
It's similar to that issue but different code in a different class altogether.