The apachesolr module (for example) lets me add my apachesolr environments to a feature. It also has code specifically intended to make it possible for users to override the settings of an apache solr environment by adding a $conf variable to settings.php. For example:
// change solr url for local testing
$conf['apachesolr_environments']['opensolr']['url'] = 'http://localhost:8080/solr/mysite';
The problem is that when i take advantage of both these options my feature - the one that includes my apachesolr environment - is (correctly) marked as overridden even though I dont want it to be. Is there some hook somewhere that I haven't figured out to let features know what is going on here? Some way to tell features to ignore certain things when deciding if a feature is overridden?
Comments
Comment #1
hefox CreditAttribution: hefox commentedNo, not really. I'd be open to adding a hook for this, but from what I recall when looking into something similair it'd be quite painful to detect (basically similair to what happens when an alter hook is used).
There is a feature request somewhere to 'lock' certain features (prevent reverting/rebuilding), but that's not this
Comment #2
bleen CreditAttribution: bleen commentedThat makes me sad ... to work around this we added this to settings.php:
Comment #2.0
bleen CreditAttribution: bleen commentedUpdated issue summary.