Several issues have surfaced recently with the new status page UI that made me start doing research what the different REQUIREMENTS variables are. Below is the current docblock:

 *   - severity: The requirement's result/severity level, one of:
 *     - REQUIREMENT_INFO: For info only.
 *     - REQUIREMENT_OK: The requirement is satisfied.
 *     - REQUIREMENT_WARNING: The requirement failed with a warning.
 *     - REQUIREMENT_ERROR: The requirement failed with an error.

This has lead to a misunderstanding of where these variables should be used, and if these variables are sufficient for the status page. This is very important for the REQUIREMENT_WARNING and REQUIREMENT_ERROR variables, where best practices require that these notices be resolved before a site can launch.

Proposed resolution

TBD - Discuss!

Remaining tasks

Define what each of these requirement notices mean
Decide if there is an area where there are gaps in messaging coverage for these notices
Identify & fix current core modules that contain notices that are miscategorized based on the definitions

User interface changes

If there is an additional notice added to core, we'd need to show it on the status report page. Otherwise, any modules who change their requirement status notices would change on the page.

API changes


Data model changes



japerry created an issue. See original summary.

japerry’s picture

See for related info of where config decided to throw a warning.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.0-alpha1 will be released the week of July 31, 2017, which means new developments and disruptive changes should now be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.