that just means your folders do not have the proper permissions to allow them to be created (the configure.php files). Just rename the configure.php.new files to configure.php and chmod 777 and re-run the installer.
You will be good to go.
2.0.4 came with blank configure.php files. 2.0.15 only comes with configure.php.new files to prevent the uninformed from overwriting their configure.php files on an upgrade.
If your server is running mod_php instead of suphp or php_cgi, php will be run as the webserver user (apache or nobody which will not have permissions to create the files on your account) you will have to have the includes folders set to world writable or rename them removing the .new from the file, and chmod them 777 to allow the new files to be created/written to by the webserver. If running suphp or php_cgi, apache/php runs as the user executing the script, so it just works without doing anything but running the installer.




LinkBack URL
About LinkBacks











Bookmarks