Problem/Motivation

The module's hook_requirements() checks whether the Drupal file folder is accessible to Drupal. When the folder is not accessible (for example, it lives on a Object Storage), the check returns REQUIREMENT_ERROR. This blocks module installation.

This breaks legitimate production deployments. The target folder may sit on a different mount, or may not be reachable yet at install time. A hard error fails the install for a condition that is valid and often temporary.

Proposed resolution

Change the severity of the inaccessible-folder condition from REQUIREMENT_ERROR to REQUIREMENT_WARNING.

  • The condition is surfaced on the Status Report but it does not block installation.
  • Report it at the runtime phase (and optionally install) as a warning, not a blocking error.
  • Keep the message clear so admins can act if the folder should be accessible.

Issue fork file_inspector-3605445

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 !4

lpeidro’s picture

lpeidro commented
Status: Active » Fixed

Apply changes.

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

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

Maintainers, credit people who helped resolve this issue.

  • lpeidro committed 52fcfe1a on 1.x 
    Resolve #3605445 "Change requirementerror"