Make entity field query optionally non alterable

Created on 22 July 2011, almost 14 years ago
Updated 17 August 2023, over 1 year ago

Originally discussed in #1164852: Inconsistencies in field language handling .

Currently entity field queries can always be altered through hook_entity_query_alter() implementations. Since update functions must be sure no hook is invoked while performing their tasks, this behavior severely limits the possibility to use entity field queries in this context.

Simply making alterability optional should solve the issue.

📌 Task
Status

Postponed: needs info

Version

9.5

Component
Field 

Last updated about 3 hours ago

Created by

🇮🇹Italy plach Venezia

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

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • 🇺🇸United States smustgrave

    Wonder if this is still a needed task for D10?

  • Status changed to Closed: outdated 3 days ago
  • 🇳🇿New Zealand quietone

    There has been no work on this task for about 13 years and no response to the question made a year ago. It is likely that it is no longer needed or has been implemented. Therefor, closing.

    If there is work to do here, then either re-open the issue and add a comment or open a new issue and reference this one.

Production build 0.71.5 2024