opus27, the googlemap module is a good example on how this should be handled. First, include the default config file. Secondly, include the real config file if it exists. This makes it easy to add new config options in newer PGV versions without losing the old configuration.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I think that this is probably the best solution that we have. One concern I have is doing that would require that the entire PGV directory be writable in order to automatically copy the default config to the user config. Unless we instruct the user to make a copy of the default config file during installation.
--John
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=1278885
How would PGV know where to look?
Logged In: YES
user_id=1006499
Originator: NO
I suggest to rename default file as : config.dist.php
On first launch, when no config.php is found a new one is created using config.dist.php
Logged In: YES
user_id=1278885
Originator: NO
opus27, the googlemap module is a good example on how this should be handled. First, include the default config file. Secondly, include the real config file if it exists. This makes it easy to add new config options in newer PGV versions without losing the old configuration.
Logged In: YES
user_id=300048
Originator: NO
I think that this is probably the best solution that we have. One concern I have is doing that would require that the entire PGV directory be writable in order to automatically copy the default config to the user config. Unless we instruct the user to make a copy of the default config file during installation.
--John