Closed (duplicate)
Project:
Strongarm
Version:
6.x-1.0-beta3
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
27 Aug 2009 at 17:59 UTC
Updated:
11 Nov 2009 at 06:47 UTC
Jump to comment: Most recent file
Comments
Comment #1
dmitrig01 commentedthere's a nifty function that does this already - it's called variable_set
Comment #2
q0rban commentedSo you don't see the value of having some default values for a feature or something that are automatically overridden if there is a value in the DB? Replaces this logic:
Comment #3
Macronomicus commentedIm keen to try the variable_set method in my feature but there may be an issue to solve first.
I want to add vars for logical defaults, but not have them erase any changes the user may have made since the last version of the feature was installed when they do an update of the feature.
Im sort of torn because I can be sure strongarm will track this and give the option to over-ride with notices... but I'm not sure all that is needed for setting pathauto & content_type tweaks that we only want an initial injection of.
Did you get any further with your idea q0rban?
Comment #4
q0rban commentedStarting work on this. Still needs lots of work but I wanted to post what I had here for when I pick it back up again. I think I may have to completely rewrite the structure of the var_conf cache in order for this to work though, as right now the form_alter disables form elements for all strongarm/weakarm vars, and we need it to only do it on strongarm vars.
Comment #5
q0rban commentedI think I like this idea better: #627924: Allow for strongarming specific key of arrayed variables
Comment #6
Macronomicus commentedCool .. thanks for the link!