Contrib.social

Figure out priorities for config event listeners

Open on Drupal.org →
Created on 21 August 2012, over 12 years ago
Updated 9 May 2025, about 13 hours ago

In #1646580: Implement Config Events and Listeners, and storage realms for localized configuration → we implemented a system of events and listeners for implementing overrides of config data (for instance for the purposes of internationalization.) A couple of open questions came out of that discussion

- How should we prioritize core implementations? These will run in a 'last executed wins' system when two listeners save to the same config data, so what should the priorities be?

- We also need to figure out priorities of the events within the systems. beejebus from that issue: "we have to consider both the priority of listeners within an event, and the order of different events across an object. so, as the patch stands, locale overrides override global conf overrides. perhaps we should collapse both of these subsystems to use the same event, something like 'config.override'?"

📌 Task
Status

Postponed: needs info

Version

11.0 🔥

Component

configuration system

Created by

🇺🇸United States gdd Portland, OR

Live updates comments and jobs are added and updated live.
  • stale-issue-cleanup

    To track issues in the developing policy for closing stale issues, [Policy, no patch] closing older issues

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.

  • Comment about 13 hours ago →
    🇺🇸United States smustgrave

    Thank you for creating this issue to improve Drupal.

    We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.

    Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

    Thanks!

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024