'State cache flag not set' requirements warning has incorrect information

Created on 22 June 2025, 16 days ago

Problem/Motivation

On D10, there is a requirements warning 'State cache flag not set', whose detail text says:

> State cache flag $settings['state_cache'] is not set. It is recommended to be set to TRUE in settings.php unless there are too many state keys. Drupal 11 will default to having state cache enabled.

This is incorrect. In Drupal 11 the state cache is permanently turned on -- see https://www.drupal.org/node/3443018 . It is not a 'default', since it can't be turned off.

Steps to reproduce

Proposed resolution

Fix the text in system_requirements().

Tagging as novice as this is a simple string change.

Remaining tasks

User interface changes

Introduced terminology

API changes

Data model changes

Release notes snippet

🐛 Bug report
Status

Active

Version

10.6

Component

system.module

Created by

🇬🇧United Kingdom joachim

Live updates comments and jobs are added and updated live.
  • Novice

    It would make a good project for someone who is new to the Drupal contribution process. It's preferred over Newbie.

Sign in to follow issues

Merge Requests

Comments & Activities

  • Issue created by @joachim
  • 🇮🇳India virag.jain

    Working on this.

  • Pipeline finished with Success
    13 days ago
    Total: 656s
    #530788
  • 🇺🇸United States smustgrave

    I thought it was clear enough to begin with but this doesn't hurt anything.

  • 🇬🇧United Kingdom joachim

    > https://www.drupal.org/node/3443018 "),
    'severity' => REQUIREMENT_WARNING,

    I don't think we normally put bare URLs like that.

    The URL is beyond the scope of this issue anyway.

  • 🇬🇧United Kingdom joachim

    @smustgrave it's currently completely wrong.

    > Drupal 11 will default to having state cache enabled.

    means that on D11 it will be enabled, unless you change a setting to make it disabled.

    In fact, on D11 it's always enabled, and there is no setting to disable it.

  • 🇺🇸United States xjm

    Thanks everyone for working on this issue. I agree that the current string is somewhat misleading, and the suggested change would improve it.

    That said, the release managers (@catc h, @quietone, and I) discussed and agreed this change does not meet our criteria for an allowed change in a maintenance minor , which would be limited to:

    • Certain critical or major bug fixes
    • Critical API compatibility backports
    • PHP and JavaScript dependency updates
    • PHP version compatibility fixes

    In this case, changing this string would require translators to also update all their translations of this string. We would only make such a break to a string in a maintenance minor if the string were actively harmful, such as telling the site owner to do something insecure.

    Therefore, I am closing the issue as "won't fix" since Drupal 11 is not affected.

    Thanks!

Production build 0.71.5 2024