In
💬
Missing schema exception on latest 8.3.x when adding view via the UI
Fixed
, I tracked the issue down to this code in DisplayPluginBase::getPlugin():
// Query plugins allow specifying a specific query class per base table.
if ($type == 'query') {
$views_data = Views::viewsData()->get($this->view->storage->get('base_table'));
$name = isset($views_data['table']['base']['query_id']) ? $views_data['table']['base']['query_id'] : 'views_query';
}
else {
$name = $options['type'];
}
The problem here is that the query plugin is updated (in the linked issue, to search_api_query), but the actual view definition still contains the default query plugin ID of views_query.
Update the $options['type'] value to have the correct plugin ID.
Per #24, it appears to ignore the actual plugin in the views config, and switches out to the one defined in the views data array. Hence an upgrade path is not needed since it would not change anything that has an effect.
Needs work
11.0 🔥
views.module
Issue summaries save everyone time if they are kept up-to-date. See Update issue summary task instructions.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
This came up as a daily bugsmash target
MR needs to be updated for 11.x
And seems the only open question is if we need an upgrade path?
With view changes don't we need to
1. Update all views
2. Do need an upgrade hook for existing sites.