Move rebuildable state information into cache system

Created on 5 August 2013, over 11 years ago

Updated 11 February 2025, 12 days ago

While working on #2040037: The requested page "/admin/appearance/settings/bartik" could not be found after installation → , I noticed that we have system.theme.data and system.*.files as information managed by the Drupal::state() service, and then we put in various workarounds to deal with the fact that that service is unavailable during installation, or the backend might throw an exception. Since this information can be rebuilt at any time from the file system, why is it not in the cache system instead? That would let us remove all those workarounds.

📌 Task

Status

Postponed: needs info

Version

11.0 🔥

Component

base system

Created by

🇺🇸United States effulgentsia

Live updates comments and jobs are added and updated live.

stale-issue-cleanup

Incomplete comments

Comments & Activities

Not all content is available!

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

Comment 12 days 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