HTTP 500 Fatal errors on admin/workbench

This also happens on latest dev and Apache 2.4.

The error is:

Fatal error: Call to a member function set() on null in core/modules/views/src/ViewExecutable.php on line 446

After a little more investigation, that page is rendering 3 block views.

Rendering just the 'workbench_current_user' block gives this error:

Fatal error: Call to a member function set() on null in core/modules/views/src/ViewExecutable.php on line 446

Rendering just the 'workbench_edited' block gives this error:

Fatal error: Call to a member function getCacheTags() on null in core/modules/views/src/Plugin/views/query/Sql.php on line 1552

Rendering just the 'workbench_recent_content' block give no errors.

This error:

Fatal error: Call to a member function set() on null in core/modules/views/src/ViewExecutable.php on line 446

happens because for some reason the workbench_current_user view doesn't exist on my site after installing workbench and workbench_moderation modules.

Related issue: #2732119: The existence of defined views is not checked

I just had

Fatal error: Call to a member function getCacheTags() on null in core/modules/views/src/Plugin/views/query/Sql.php on line 1552

from another view that I created myself and it seemed to be directly related to having a relationship from the content revision to the content.

I have not done a search for related Drupal core issues yet.

Duplicate of the linked issue.

I believe only the "Call to a member function set() on null" error was a duplicate but this one still happens, and I think it relates to having a relationship from the content revision to the content.

Fatal error: Call to a member function getCacheTags() on null in /var/www/exp/core/modules/views/src/Plugin/views/query/Sql.php on line 1552

Possibly there is another issue for that somewhere but I haven't had an in depth look into it yet.

Related #2738051: \Drupal\views\Plugin\views\query\Sql::getCacheTags and getCacheMaxAge don't take into account that some entities can be NULL

"from another view that I created myself" is not an issue for this queue.

But it also happens with the view provided by this module. The workbench_edited view. That's what this is about. See comment #4.

That statement was just to illustrate that it is possibly related to the content revision relationship.

I can't replicate this error. The linked issue was caused when content translations were active.

Two questions:

1) Are you using content translation? Any other modules or configuration that might affect the view?

2) Are you testing against alpha2 or dev?

I have the same issue, happens when the user have multiple nodes published and I am using the alpha version.
There are no modules that modify that view.
Tested with php versions from 5.5 to 7and always same result.

Also if one of the devs need access to my current website to see the problem, plscontactme by pm and we can arrange it.

I still can't replicate this.

A module like Content Translation might not modify the View, but it could modify node properties or caching in a specific way, so I still need to know what modules are installed.

Perhaps an export of your content type config would help.

Here you have a full config export of my site (wip, so some of things on it atm), hope it helps

It's possible that this fix will solve it: #2714989: Views which load the same entity type as entity and non default revision cause fatal in Sql::getCacheTags()

I can confirm that the patch mentioned in #18 has fixed this issue for me

And that patch should be included in Drupal 8.1.5, so an upgrade should fix the issue.