\Drupal\views\Plugin\views\HandlerBase contains this gem:
public function ensureMyTable() {
if (!isset($this->tableAlias)) {
$this->tableAlias = $this->query->ensureTable($this->table, $this->relationship);
}
return $this->tableAlias;
}
The $this->query property is documented as an instance of \Drupal\views\Plugin\views\query\QueryPluginBase, which does not have an ensureTable() method, however. The only real subclass of QueryPluginBase is the Sql implementation which has the ensureTable() method. The QueryTest test implementation has an empty ensureTable() method, probably because it is required due to this bug.
The
Search API →
module provides an alternate views query plugin, which does not provide an ensureTable() method leading to fatal errors.
?
Needs work
10.1 ✨
Last updated
It denotes an issue that prevents porting of a contributed project to the stable version of Drupal due to missing APIs, regressions, and so on.
There is consensus among core maintainers that this is a major issue. Only core committers should add this tag.
Used to track the progress of issues reviewed by the Drupal Needs Review Queue Initiative.
A change record needs to be drafted before an issue is committed. Note: Change records used to be called change notifications.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
This issue is being reviewed by the kind folks in Slack, #needs-review-queue-initiative. We are working to keep the size of Needs Review queue [2700+ issues] to around 400 (1 month or less), following Review a patch or merge request → as a guide.
Think instead of removing it should be deprecated first
#41 applies but had a bunch of failures
Definitely think it will need a change record.