This prevents the flickering of multiple select filters although might not be the ultimate solution
In our case, this manifested as the incorrect revision being marked as the default revision
This is exactly how it showed up in our case as well, but after digging (far) deeper into it turned out it doesn't matter whether entity supports revisions or not.
showing stale information to end-users on the front-end.
I'm sure majority of us has been there and just cleared cache without thinking twice. "Luckily" in our case the outcome was more site-breaking by affecting entities that are not manually editable. Looking back with what I know now, I'm sure I've met the same issue before.
Seems to reproduce with latest vanilla as well
Can confirm RTBC.
FYI: this is really annoying, Drupal shows these warnings to ALL users :-/
Drupal, in fact by default doesn't do that. You might want to check that you don't have developer settings turned on where you don't want them. Here's couple handy links for you
https://www.drupal.org/docs/develop/development-tools/enable-verbose-err... →
Got the same error and can confirm #2 fixing the issue.
Apparently even the most trivial fix can go wrong when done in hurry :)
Leaving open for someone to try out patching
Trivial fix of the year.
Thanks for the patch!
This was actually in the todo pile ever since I realized it's different field type entirely.