Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Now that the entity reference fields added by Entityqueue are not locked and are configurable, there's a lot of potential for confusion around the bundle filtering, because you can specify the bundle filtering both in the queue settings and in the field settings.
This can cause problems because if any filtering is specified in either place, the *combination* of the two settings get added to the entity field query.
To avoid this problem, we should not allow bundles to be selected on the field settings form if the "Entity Selection" mode is set to Entityqueue.
Comment | File | Size | Author |
---|---|---|---|
#3 | 2929030-hide-bundles2.patch | 4.47 KB | quicksketch |
#2 | 2929030-hide-bundles.patch | 3.03 KB | quicksketch |
Comments
Comment #2
quicksketchPatch that hides the settings and replaces it with a description of where the bundles may be set.
Comment #3
quicksketchSlightly further reworked patch that also warns you shouldn't use the Entity Queue selection mode on any entity type other than an Entity Queue.
Comment #5
quicksketchCommitted to 7.x-1.x.
Comment #7
amateescu CreditAttribution: amateescu for Pfizer, Inc. commentedNoting here for posterity: this patch broke the entityqueue selection handler because it doesn't take all the core overrides for
buildEntityFieldQuery()
into account anymore. Fixed in #2949180: The entityqueue selection handler doesn't take all the core overrides into account.