The information generated by the module is very interesting, but it requires someone to interpret it to draw conclusions.

It would be great if any conclusions that could potentially cause errors or have a negative impact on the site were communicated to users in the Drupal Status Report, as other modules do.

Issue fork xray_audit-3467105

Command icon 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:

About issue forks

Comments

lpeidro created an issue. See original summary.

lpeidro opened merge request !36

lpeidro’s picture

lpeidro commented

Status:

The plugin has been defined, and the system for implementing insights has been established.

Two insights have been implemented:

  • one that detects content entity bundles with no content, and
  • another that detects custom modules that are not enabled and may therefore be candidates for removal.

Only local images are allowed.

I think we can merge this issue when it is ready. If we need to add new insights, we can implement them in a new issue.

Ready for testing.

lpeidro’s picture

lpeidro commented
Status: Active » Needs review
sadysierralta’s picture

sadysierralta commented

Mr looks great to me

  • lpeidro committed bd875dcd on 1.x 
    Issue #3467105: Create submodule Xray Insights and plugin system to...
lpeidro’s picture

lpeidro commented
Status: Needs review » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.