Closed (won't fix)
Project:
Strongarm
Version:
6.x-2.0-beta1
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
5 Dec 2009 at 09:59 UTC
Updated:
23 Sep 2010 at 20:09 UTC
I like how "weakarm" is the default setting in strongarm 2.0. However, there are situations where having a specific variable configuration is critical to a site functioning properly. In a Features module export, I tried setting the following code to TRUE:
$strongarm->disabled = FALSE; /* Edit this to true to make a default strongarm disabled initially */
There was no effect. Based on the strongarm 2.0 blog post, I suspect the functionality has been removed and this is just legacy code. Please bring the functionality back as an opt-in option! Ideally, there would be an associated permission so administrators can decide what users groups can change sensitive strongarm variables.
Comments
Comment #1
jmiccolis commentedI think you mis-understand the disabled flag - I believe that is added by ctools and dictates whether the exported value should be used or not. This is the same concept as being able to 'disable' a views module view.
Yes the ability to strongly force a value has been removed (I know, this totally runs counter to the name of the module!). I'd actually like to avoid bringing it back. I'm beginning to think that the permission system is the proper place to hand these sorts of questions. So that if a user shouldn't have access to a setting they don't receive the permission to change it.
I'm tentatively marking this as "won't fix".
Comment #2
grendzy commentedI see your point, but there are many variables that are controlled by "administer site configuration", and so sometimes it's useful to be able lock things with more granularity.
Comment #3
Grayside commentedThat's a good point, and that would be nice functionality. Maybe the need is for another module that uses a "administer locked site configuration" and a hook_variable_lockbox() to set access control.
In that way, you could use Strongarm to export the variables and "Variable Lockbox" to then hide those settings from everyone not an administrator.
I could see that being used to take away the dangerous/confusing elements of a site configuration once core stuff is set.
Comment #4
achtonDoes this mean that there is no way to force variables to take effect? E.g. force site_name, even if the value was set previously?
Comment #5
Grayside commentedYes.
However, it seems to me it wouldn't be hard to write an install hook that invoked hook_strongarm and funnel the results into variable_set().
Or simply use variable_set() for the specific value you desire.