Timeline for How do I programmatically change settings to simplify sharing of config changes?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 28, 2013 at 3:15 | comment | added | Charlie Schliesser | @iconoclast In my experience, the above mentioned solutions can fall short in encapsulating all of the settings that one might make on a dev server, and even minor settings being missed force you to retrace your steps. An example would be field formatter settings being missed, nested fieldsets, etc. These are things I've encountered, at least. | |
| Aug 20, 2012 at 21:27 | comment | added | iconoclast | @berkes: I'd love to hear more explanation as to how and where the above solutions fall short. | |
| Dec 12, 2011 at 15:03 | comment | added | berkes | I would say (with the risk of starting a flamewar) that all abovementioned "solutions" are incomplete, unstable or get your only so-far. There is simply no working solution, and the reason for that, lies deep in the architecture of Drupal itself. Abovementioned solutions don't fix the problem, they merely supress the symptoms that problem causes. The only solution I found so far is simply "re-do the configuration". "And again in test". "And again on production". "And on every developers setup". | |
| Nov 29, 2011 at 16:55 | comment | added | user842 | Yes. that is correct. | |
| Nov 29, 2011 at 10:41 | vote | accept | Sam Murray-Sutton | ||
| Nov 29, 2011 at 10:41 | comment | added | Sam Murray-Sutton | Best answer possible, given current state of Drupal, so I'm going to accept it... I like the thought of using features to encapsulate a given configuration and then sharing that between team members - that kind of thing ought to be possible right? | |
| Nov 24, 2011 at 19:18 | history | edited | user842 | CC BY-SA 3.0 |
added 69 characters in body
|
| Nov 24, 2011 at 19:10 | history | answered | user842 | CC BY-SA 3.0 |