Add report section for modules with an installed schema version entry but not found in the filesystem.

Created on 8 September 2020, almost 4 years ago
Updated 30 January 2023, over 1 year ago

Problem/Motivation

Disable a module locally, export config, remove module code.
Deploying the change to core.extension to a production site, the config import will disable the module, but since the code was already removed, hook_uninstall will not run and the installed schema version entry stays in the database.

A user error on the status reports page informs the user about this issue, unfortunately when error reporting is turned off as it tends to be on production environments, this will not be shown.
There already is a report section for modules listed in core.extension but not found in the filesystem.

Proposed resolution

Add report section for modules with an installed schema version entry but not found in the filesystem.

✨ Feature request
Status

Needs work

Version

10.1 ✨

Component
SystemΒ  β†’

Last updated 1 day ago

No maintainer
Created by

πŸ‡©πŸ‡ͺGermany volkerk

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

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

  • The Needs Review Queue Bot β†’ tested this issue. It either no longer applies to Drupal core, or fails the Drupal core commit checks. Therefore, this issue status is now "Needs work".

    Apart from a re-roll or rebase, this issue may need more work to address feedback in the issue or MR comments. To progress an issue, incorporate this feedback as part of the process of updating the issue. This helps other contributors to know what is outstanding.

    Consult the Drupal Contributor Guide β†’ to find step-by-step guides for working with issues.

Production build 0.69.0 2024