ciano:
Hi. As Mark already pointed out, it's important to know the permissions and the owner of the CMS document-root directory. That message means the instruction "MKDIR" failed. If you want to know the exact message, edit the adm_mkroot.php and create.php files, deleting the "@" before the "mkdir" instruction (around lines 50 and 207, respectively, if using 0.6.0b12 version).
The two common causes are:
1) Lack of writting permissions in the directory.
2) PHP running in safe-mode and the owner of the scripts is not the same than the webserver-user.
For the first problem, just follow the directions in the install.txt file:
Quote:
Change the ownership of those files to the user used by your web server (usually "nobody" in Unix/Linux). To change the ownership in Linux/Unix, you execute in a shell terminal in the server the command chown:
chown -h -R nobody:nobody cm/
In Windows environments, using the Windows Explorer, check the Security tab of the Properties dialog of the directory, and set the permissions so that the user IUSR_servername has permissions to read and write on the CM directory.
For the second problem, if you are the administrator of the server, just change the ownership of the files or disable safe-mode (and use other kind of protection like open-basedir). However, if you are using a hosting service, that will be quite problematic. The CMS module is mostly impossible to install and use in safe-mode with hosting services (unless the administrator helps you).
Why? Because most hosters give you an account and run the webserver a different user. So you upload your files (which now belong to your user). Then, when PHP is asked to MKDIR, it will check the ownership of the directory (your user) and the identity of the running process (the webserver user) and will fail with a safe-mode error.
But, please, give us more information.
Regards,
Mario A. Valdez-Ramirez.
Login
FAQ
Search
