Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Problem/Motivation
Currently on the status report the xray_audit insight is shown submodules not enabled, maybe those modules can be ignored, as some contrib modules have multiples submodules that are optional and can not be removed.
Report example:
The following custom and/or contrib modules are not enabled (Modules Report):
Modules contrib not enabled:
Facets Range Widget, Rest Facets, Facets Searchbox Widget
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | example-submodule-no-project.png | 73.24 KB | lpeidro |
Issue fork xray_audit-3479115
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:
changes
Comments
Comment #2
lpeidro commentedThere is a logic to exclude submodules by checking the project set in the info.yml, which does not seem to be effective in the case of the Facets module, where the project parameter is not set.For example, if Webform is used in the project, the disabled submodules are not displayed.
It is necessary to review the logic to make it much more refined.
Sorry, in my initial judgment I was mistaken.
The issue lies in the fact that, as I mentioned, to check if it is a submodule or not, we were checking the module's project.
However, the project's info is not inserted by the contributor in the .info file, but is automatically added during the release generation process.
Therefore, in those cases where disabled submodules are shown, it is because the development version is installed instead of the release version.
It is necessary to review the logic to make it much more refined.
Comment #3
lpeidro commentedAn additional check has been added in case the project is not defined in the module, by verifying the module's path. However, this solution might still fail to detect some cases if the development version is installed. A 100% reliable logic would require a certain computational cost, which could be an inconvenience for Drupal status reports.
Comment #6
lpeidro commentedComment #7
eduardo morales albertiThank you @lpeidro