Problem/Motivation
After installing Drupal 11.3 via CMS 2, admin/reports/status reports this error:
Errors Found: Package Manager
Package Manager is available for early testing. To install the module set the value of 'testing_package_manager' to TRUE in your settings.php file
So the error assumes that the package manager module has not been installed, but actually it has been installed by a Drupal CMS recipe.
The term "error" is misleading because it might cause the Drupal user to worry that something has gone wrong with the installation.
core/modules/package_manager/src/Hook/PackageManagerRequirementsHooks.php :
if (Settings::get('testing_package_manager', FALSE) === FALSE) {
$requirements['testing_package_manager'] = [
'title' => $this->t('Package Manager'),
'value' => $this->t('Not protected'),
'description' => $this->t("Package Manager is available for early testing. To install the
module set the value of 'testing_package_manager' to TRUE in your settings.php file."),
'severity' => REQUIREMENT_ERROR,
];
}
Steps to reproduce
Install CMS 2, go to admin/reports/status
Proposed resolutions
- check whether package_manager module is enabled before triggering this error
- change the error description
- downgrade severity from REQUIREMENT_ERROR to REQUIREMENT_WARNING
Issue fork drupal-3573464
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
- 3573464-misleading-error-concerning
compare
- 3573464
changes, plain diff MR !14959
Comments
Comment #2
phenaproximaDon't have time to work on it myself, but +1 for this change. Enabling Package Manager while it's in early testing should not be an error. Nothing is wrong, after all; it's just something to be aware of.
Comment #4
juc1 commentedComment #5
phenaproximaThis, in my opinion, is a no-brainer.
Package Manager being enabled for early testing, even if the setting has not been tweaked, isn't an error. It's certainly something to be aware of, and therefore a warning makes sense -- but otherwise, everything is still operational as far as the site administrator need be concerned. They need take no action.
RTBC on the assumption that tests will pass.
Comment #6
catchCommitted/pushed to main, 11.x and 11.3.x, thanks!