When a new module is created, the author will include a configuration file with default values. When the module is installed, this file will be copied to the config directory and read into the active store. Future changes will be written to the file in the config directory. This whole process needs to be implemented. I think that one of the big questions is how these files will be discovered. My preference would be that we look for a specially named directory like 'config' and just consider anything in there with a defaut.xml file name to be config that gets moved to the active area. Later we may want to do something where the config files are more specifically declared (in the info file maybe) but I think we can hold that for later.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Xen’s picture

Status: Active » Needs review
FileSize
1.45 KB

Latest head has code that almost works. This really works.

gdd’s picture

Ah I was working on fixing this, but your version is a lot simpler. I'm going to commit this right now.

naxoc’s picture

Status: Needs review » Reviewed & tested by the community

Yes it works. The installer does not die now anymore.

gdd’s picture

Status: Reviewed & tested by the community » Fixed
Xen’s picture

Status: Fixed » Needs review
FileSize
1.75 KB

Passing by the code, I thought this is a bit more elegant.

Xen’s picture

Oh, and

        $drupal_config_dir = config_get_config_directory();

should be removed, it's not used.

sun’s picture

Status: Needs review » Fixed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.