confusing file naming config.php config2.php

**hm2k** · 11-16-2006, 02:39 PM

config.php is not a configuration file, you are not meant to edit any aspect of this.
config2.php is the configuration file, you are meant to edit this.

After looking at both of these files I soon realised why they existed in this way.

At one point config.php contained some configuration settings, but they appear to have moved into config2.php.

I'm proposing that config2.php should be renamed to something like "settings.php" in future versions making it easier to identify.

It seems the only place that config2.php is included is is in config.php anyway, so it would be easy to make this transition.

**AshDigg** · 11-16-2006, 05:39 PM

Sounds good to me.

**hm2k** · 11-20-2006, 06:03 AM

I also proposed that the configs/settings could be placed into the database...

http://www.pligg.com/forum/showthread.php?t=2666

This is something for the future though.

I look forward to the implementation(s).

**kbeeveer46** · 11-20-2006, 07:21 AM

Originally Posted by hm2k

I look forward to the implementation(s).

It would work a lot faster if you actually did anything about everything you propose. Just because you propose it doesn't mean that it's automatically going to be implemented.

**hm2k** · 11-21-2006, 03:09 PM

Originally Posted by kbeeveer46

It would work a lot faster if you actually did anything about everything you propose. Just because you propose it doesn't mean that it's automatically going to be implemented.

And how do you propose I implement them, I don't have access rights. I've already implemented it locally.

PS. I discovered that this change would need to be changed in install/install3.php and install/upgrade.php and the readme file -- is anyone aware of anywhere else?