Problem/Motivation

When the message "There are errors with some installed modules. Visit the status report page for more information." is displayed in response to a component missing the "core_version_requirement" key, and the component in question is the site profile, no additional details are displayed on the Status Report Page, leaving the site administrator with no idea where the problem is coming from.

This message was added as part of issue #3123537: /admin/reports/status should not WSOD if it finds an extension missing core_version_requirement in its info.yml file.

Steps to reproduce

Remove the "core_version_requirement" key from your custom site profile and then visit the "Extend" admin page.

Proposed resolution

I would imagine the code is pulling all components (modules, themes, profiles) to check for that "core_version_requirement" key, but is only processing modules when it comes to injecting messages into the Status Report. Either the Extend page needs to exclude everything not a module from the "core_version_requirement" check, or the code for the Status Report needs to explicitly check profiles and display a message about what is wrong.

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

Comments

iacwebdev created an issue. See original summary.

cilefen’s picture

cilefen commented
Component: base system » extension system
Webbeh’s picture

Webbeh
he/him/his
Location Georgia, USA
commented
Issue summary: View changes

Version: 9.1.x-dev » 9.3.x-dev

Drupal 9.1.10 (June 4, 2021) and Drupal 9.2.10 (November 24, 2021) were the last bugfix releases of those minor version series. Drupal 9 bug reports should be targeted for the 9.3.x-dev branch from now on, and new development or disruptive changes should be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.15 was released on June 1st, 2022 and is the final full bugfix release for the Drupal 9.3.x series. Drupal 9.3.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.4.x-dev branch from now on, and new development or disruptive changes should be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.9 was released on December 7, 2022 and is the final full bugfix release for the Drupal 9.4.x series. Drupal 9.4.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.5.x-dev branch from now on, and new development or disruptive changes should be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

nicxvan’s picture

nicxvan commented
Status: Active » Postponed (maintainer needs more info)

Can someone confirm this is still happening please?

Should be straightforward to add to hook_runtime_requirements.

iacwebdev’s picture

iacwebdev commented

Well, it seems like after four and a half years it's become something of a moot point. At least, I tried to do a test against the most recent release of Drupal 11 (11.2.5), but when I removed the 'core_version_requirement' key from the site's custom profile and tried to clear caches, the site went WSOD on me. Not sure if that's related to the connected issue above or not, as that one looks to have been resolved back with Drupal 9, though I couldn't discern exactly what kind of fix was implemented.

In any case, I don't know how to test now, but I suppose the WSOD and the error in the logs that made it clear Drupal wasn't happy about the missing 'core_version_requirement' key in the profile's info.yml file make it pretty clear to admins now what's wrong and what needs to be fixed. I'm not sure going from a detail-less error message to a WSOD is an improvement, but I suppose at this point not too many people will be dealing with profiles that are old enough to still be missing the 'core_version_requirement' key.

nicxvan’s picture

nicxvan commented
Status: Postponed (maintainer needs more info) » Closed (works as designed)

Thank you for coming back to test after all of this time!

Yes I think this is the expected behavior at this point.

I'm going to close this for now as works as designed.

Now that this issue is closed, please review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, please credit people who helped resolve this issue.