Contrib.social

Views using Entityqueue do not return results when Workspaces is enabled

Open on Drupal.org →
Created on 29 May 2025, 3 months ago

Problem/Motivation

When the Workspaces module is enabled, Views that use an Entityqueue relationship and filter fail to return any results, even when content exists in the queue. This appears to be a compatibility issue between Entityqueue and Workspaces.

This issue is present on a site running Drupal 10.4.7 with Workspaces enabled, and Entityqueue version 8.x-1.9.

Steps to reproduce

  1. Enable both the Entityqueue and Workspaces modules.
  2. Create a new entityqueue and add one or more nodes to that queue.
  3. Create a View that displays content of the type added to the queue.
    • At this point, the view correctly displays content.
  4. Add a Relationship: Content queue, and select the entityqueue created in step 2.
    • The view still correctly displays content.
  5. Add a Filter Criteria: Entityqueue: Content In Queue and set it to Yes.
    • After adding this filter, the view no longer displays any content, even though nodes are present in the queue.

Here is the query for a view which includes a queue as a filter criteria prior to Workspaces being enabled:

SELECT "entity_subqueue__items"."delta" AS "entity_subqueue__items_delta", "node_field_data"."nid" AS "nid", "items_node_field_data"."name" AS "items_node_field_data_name"
FROM
{node_field_data} "node_field_data"
LEFT JOIN {entity_subqueue__items} "entity_subqueue__items" ON node_field_data.nid = CAST(entity_subqueue__items.items_target_id AS UNSIGNED) AND entity_subqueue__items.bundle = 'large_feature_slider'
LEFT JOIN {entity_subqueue_field_data} "items_node_field_data" ON entity_subqueue__items.entity_id = items_node_field_data.name
WHERE ("node_field_data"."status" = '1') AND ("node_field_data"."type" IN ('feature_slide')) AND ((entity_subqueue__items.items_target_id IS NOT NULL))
ORDER BY "entity_subqueue__items_delta" ASC
LIMIT 3 OFFSET 0

...and here is the query for the same view after the Workspaces module has been enabled:

SELECT "entity_subqueue__items"."delta" AS "entity_subqueue__items_delta", "node_field_data"."nid" AS "nid", "items_node_field_data"."name" AS "items_node_field_data_name"
FROM
{node_field_data} "node_field_data"
LEFT JOIN {entity_subqueue__items} "entity_subqueue__items" ON node_field_data.nid = CAST(entity_subqueue__items.items_target_id AS UNSIGNED) AND entity_subqueue__items.bundle = 'large_feature_slider'
LEFT JOIN {entity_subqueue_field_data} "items_node_field_data" ON entity_subqueue__items.entity_id = items_node_field_data.name
WHERE (("node_field_data"."status" = '1') AND ("node_field_data"."type" IN ('feature_slide')) AND ((entity_subqueue__items.items_target_id IS NOT NULL))) AND (("entity_subqueue__items"."revision_id" IN (SELECT MAX(entity_subqueue_revision.revision_id) AS "revision_id"
FROM
{entity_subqueue_revision} "entity_subqueue_revision"
WHERE "revision_default" = '1')) OR ("entity_subqueue__items"."revision_id" IS NULL))
ORDER BY "entity_subqueue__items_delta" ASC
LIMIT 3 OFFSET 0

Proposed resolution

It appears that when Workspaces is enabled, Views that join against entity_subqueue__items are affected by additional revision-based conditions that interfere with expected results. Specifically, Views adds the following clause when Workspaces is enabled:

AND (("entity_subqueue__items"."revision_id" IN (SELECT MAX(entity_subqueue_revision.revision_id) AS "revision_id"
FROM
{entity_subqueue_revision} "entity_subqueue_revision"
WHERE "revision_default" = '1')) OR ("entity_subqueue__items"."revision_id" IS NULL)

This clause seems incompatible with how Entityqueue currently stores or relates its items in Views, especially when the “Content in queue” filter is used.

A possible resolution might involve updating the Views relationship plugin for entityqueue to properly account for revisions and workspace context, similar to how revision-aware entities (like nodes or paragraphs) handle it.

Remaining tasks

User interface changes

API changes

Data model changes

🐛 Bug report
Status

Active

Version

1.9

Component

Code

Created by

🇺🇸United States butterwise

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @butterwise
  • Comment 2 months ago →
    marcus.w

    I'm seeing the same issue 1.8 is ok 1.9 introduces the issue

  • Comment 2 months ago →
    🇺🇸United States butterwise

    Confirming @marcus.w's report: Rolling back to 8.x-1.8 allows Workspaces to be enabled and the views using entityqueue to function as expected.

    Having said that, when working in a workspace, any changes made to an entityqueue (adding or removing an item or reordering items) result in a 500 error:

    The website encountered an unexpected error. Try again later.

Drupal\Core\Entity\EntityStorageException: SQLSTATE[HY000]: General error: 1366 Incorrect integer value: 'my_entityqueue' for column 'target_entity_id' at row 1: INSERT INTO "workspace_association" ("workspace", "target_entity_revision_id", "target_entity_type_id", "target_entity_id") VALUES (:db_insert_placeholder_0, :db_insert_placeholder_1, :db_insert_placeholder_2, :db_insert_placeholder_3); Array ( [:db_insert_placeholder_0] => 0363dcf2-de53-430d-9804-a5eb22494101 [:db_insert_placeholder_1] => 8 [:db_insert_placeholder_2] => entity_subqueue [:db_insert_placeholder_3] => my_entityqueue ) in Drupal\Core\Entity\Sql\SqlContentEntityStorage->save() (line 817 of core/lib/Drupal/Core/Entity/Sql/SqlContentEntityStorage.php).
Drupal\Core\Database\StatementWrapperIterator->execute() (Line: 44)
Drupal\mysql\Driver\Database\mysql\Insert->execute() (Line: 141)
Drupal\workspaces\WorkspaceAssociation->trackEntity() (Line: 55)
Drupal\wse\WseWorkspaceAssociation->trackEntity() (Line: 233)
Drupal\workspaces\EntityOperations->entityUpdate() (Line: 160)
workspaces_entity_update()
call_user_func_array() (Line: 416)
Drupal\Core\Extension\ModuleHandler->Drupal\Core\Extension\{closure}() (Line: 395)
Drupal\Core\Extension\ModuleHandler->invokeAllWith() (Line: 423)
Drupal\Core\Extension\ModuleHandler->invokeAll() (Line: 217)
Drupal\Core\Entity\EntityStorageBase->invokeHook() (Line: 900)
Drupal\Core\Entity\ContentEntityStorageBase->invokeHook() (Line: 564)
Drupal\Core\Entity\EntityStorageBase->doPostSave() (Line: 781)
Drupal\Core\Entity\ContentEntityStorageBase->doPostSave() (Line: 489)
Drupal\Core\Entity\EntityStorageBase->save() (Line: 806)
Drupal\Core\Entity\Sql\SqlContentEntityStorage->save() (Line: 354)
Drupal\Core\Entity\EntityBase->save() (Line: 282)
Drupal\entityqueue\Form\EntitySubqueueForm->save()
call_user_func_array() (Line: 129)
Drupal\Core\Form\FormSubmitter->executeSubmitHandlers() (Line: 67)
Drupal\Core\Form\FormSubmitter->doSubmitForm() (Line: 597)
Drupal\Core\Form\FormBuilder->processForm() (Line: 326)
Drupal\Core\Form\FormBuilder->buildForm() (Line: 73)
Drupal\Core\Controller\FormController->getContentResult() (Line: 80)
Drupal\workspaces\Controller\WorkspacesHtmlEntityFormController->getContentResult()
call_user_func_array() (Line: 123)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->Drupal\Core\EventSubscriber\{closure}() (Line: 638)
Drupal\Core\Render\Renderer->executeInRenderContext() (Line: 124)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->wrapControllerExecutionInRenderContext() (Line: 97)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->Drupal\Core\EventSubscriber\{closure}() (Line: 181)
Symfony\Component\HttpKernel\HttpKernel->handleRaw() (Line: 76)
Symfony\Component\HttpKernel\HttpKernel->handle() (Line: 53)
Drupal\Core\StackMiddleware\Session->handle() (Line: 48)
Drupal\Core\StackMiddleware\KernelPreHandle->handle() (Line: 28)
Drupal\Core\StackMiddleware\ContentLength->handle() (Line: 116)
Drupal\page_cache\StackMiddleware\PageCache->pass() (Line: 90)
Drupal\page_cache\StackMiddleware\PageCache->handle() (Line: 48)
Drupal\Core\StackMiddleware\ReverseProxyMiddleware->handle() (Line: 51)
Drupal\Core\StackMiddleware\NegotiationMiddleware->handle() (Line: 36)
Drupal\Core\StackMiddleware\AjaxPageState->handle() (Line: 51)
Drupal\Core\StackMiddleware\StackedHttpKernel->handle() (Line: 741)
Drupal\Core\DrupalKernel->handle() (Line: 19)
  • Comment 15 days ago →
    mvnovick

    I am seeing the same issue with Drupal 10.4.8 and Entityqueue 8.x-1.9. When the Workspaces module is enabled, content queue relationships stop working in views. In my particular case, I was able to temporarily get around this bug by making sure that the queue in my view was the last one created on the site, so that MAX(entity_subqueue_revision.revision_id) would match my queue. This approach will obviously not work if multiple queues need to be used in view relationships.

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024