It should be possible to disable the module, but still have it installed

Created on 25 March 2017, almost 8 years ago
Updated 16 August 2024, 5 months ago

Moving around configuration is a normal workflow for drupal sites - but you want modules to behave different in different environments, but still have them activated (as part of core.extension.yml). So a disabled option would solve that if you have stage file proxy on in a prod. environment as an example.

Added a checkbox for this on the config page.

Override in settings.php, or settings.local.php - this will disable stage file proxy from fetching missing images with proposed patch.

$config['stage_file_proxy.settings']['disabled'] = 1;
✨ Feature request
Status

Closed: works as designed

Version

1.0

Component

Code

Created by

πŸ‡ΈπŸ‡ͺSweden MiSc

Live updates comments and jobs are added and updated live.
  • Needs tests

    The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.

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.

  • πŸ‡ΊπŸ‡ΈUnited States freelock Seattle

    FWIW, Reroute Email uses this pattern, as do a bunch of commerce module -- a global "enable" config that can act as a kill switch. It's a really handy pattern.

    Config Split introduces a ton of complexity and confusion to managing configuration -- which means opportunities to make mistakes. We highly prefer a global config with specific environment overrides -- this allows us to have sane settings in the database for all dev environments, and hard-code specific overrides for production in a production-specific environment file.

    Even better is being able to set these with environment variables, but that's an entirely different topic...

Production build 0.71.5 2024