Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
I'm curious why this feature was removed http://drupalcode.org/project/shield.git/blobdiff/5dacfc804508a76c3fbd0d...
It seems like a good feature to me.
Comment | File | Size | Author |
---|---|---|---|
#1 | 1394326_bring_back_state.patch | 872 bytes | greggles |
Comments
Comment #1
gregglesThis is just a
git diff 5dacfc8 -R
The scenario where I want to use this:
* My dev site is an automatic copy of my live site
* My dev site has a different settings.php which points at a different DB
* I can do
$conf['shield_state'] = 1;
in settings.php so the module settings are the same on all sites, but it's only actually enabled on devComment #2
chx CreditAttribution: chx commentedWhy would shield reproduce what http://drupal.org/project/environment_modules can do?
Comment #3
pkiraly CreditAttribution: pkiraly commentedA short history: the original idea of the triggering the status on/off was initiated by NeverGone, see http://drupal.org/node/1369404. The idea was implemented, then dicussed and finally rejected at #drupal.hu IRC channel.
Comment #4
gregglesThere is no need for this, given environment_modules.
Thanks for documenting it on the project page, pkiraly :)
Comment #5
geek-merlinI've looked into environment_modules and it's a dirty hack that works in some cases, but messes with hook_boot in a way that can mess up a lot of stuff. Read source.
From the project page:
And
So i think in fact environment_modules should depend on bad_judgement and this feature makes sense.
Comment #6
geek-merlinIn fact this was implemented in #1604808: Disable checkbox on admin page and is in dev release.