Michal Čihař a écrit :
Hi
On Thu 8. 9. 2005 14:57, Marc Delisle wrote:
I agree with your first idea. We could even do this: at run time, if config.inc.php is not there, try to create it from config.default.php and inform the user if it works or if it fails (could fail because of safe mode restrictions or just permission problems).
Why to create it? We can just work when file is not existing. Creating file will anyway fail in most cases.
Why create it? To avoid many support questions. Unless you tell me that PMA could work without a config.inc.php. Which might be an interesting idea: config.inc.php would really be config_local.inc.php?
This way, we keep the current behavior that a default PMA installation works immediately without doing anything, permitting to connect to a default MySQL installation with root and no password (yeah!).
What is quite usual configuration on devel machines :-).
And many productions machines unfortunately!
Note that at some places in the code we set some parts of $cfg dynamically based on the MySQL version, but this should not be a problem.
This is done anyway somewhere later.
Let's not forget also config.inc.developer.php :)
Yes: Let's not forget to remove also config.inc.developer.php :)
Ok, I see, because config.inc.php would not be in CVS anymore.
See also https://sourceforge.net/tracker/index.php?func=detail&aid=1253493&gr... up_id=23067&atid=377410
Looks interesting.
I'm currently (finally) working on new import system. I guess I could get to configuration stuff just after that. I have quite lot of time for coding right now as I'm ill at home ;-).
Take care!
Marc