Posted by John Pitcairn on October 30, 2009 at 1:49am
Jump to:
| Project: | Virtual Sites |
| Version: | 6.x-1.3 |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
Wondering why the custom variables for each virtual site get messed up when a site is moved, I discovered there is an actual INI file for each virtual site, stored in a filesystem directory. Not really what I would expect for something that is a configuration option, and it makes staging sites to/from the production server just one step more tedious (I don't commonly need to migrate anything in the private filesystem).
Any chance the variable overrides could be written to the database, not stored as a file?
I'll take a look at it myself if I get some spare time (yeah, right).
Comments
#1
The reason seems to be that Drupal 6 only had a helper function to read and interpret .ini files from the filesystem. As there is a new convenience function to do it for any data in Drupal 7, this is already solved in 7.x.