installer

Checking if assets/export directory exists: OK!
Checking if assets/export directory is writable: Failed!
Checking if manager/includes/config.inc.php is writable: Failed!
For new Linux/Unix installs, please create a blank file named config.inc.php in the manager/includes/ directory with file permissions set to 777.

Ok, so why isn’t this file already created? Is it some kind of security measure?
Aslo why does the bold message come after the checking. I wonder if this message shouldn’t come earlier in the install process.

Just a few comments

@ edit @
IF everything checks fine ... could we just skip that click?

installer won’t erase my install directory ...

This is a great opportunity for you to demonstrate your coding prowess Carsten. None of the delete or create functions work in the Linux/BSD/OS X worlds... care to take a crack at getting it to do so?

Although I don’t know why it doesn’t in reality. The file manager works with these types of functions.

Interesting ... I wonder if this works on 10.3?

The config.inc.php file is not shipped with modx. This is to prevent the system from overwritting the config.inc.php file of an existing install.

On some system namely linux MODx will not be able to delete the installer folder due to file security settings.

Ryan,

Maybe we should add a check list to the installation guide?

Quote from: rthrash at Jul 26, 2005, 12:32 PM

This is a great opportunity for you to demonstrate your coding prowess Carsten. None of the delete or create functions work in the Linux/BSD/OS X worlds... care to take a crack at getting it to do so?

Although I don’t know why it doesn’t in reality. The file manager works with these types of functions.

Actually, this does work on my hosting service, which is Linux. However, the issue is how the hosting is configured. Until recently, this would not have worked at all, but config changes to the server now allow ftp uploads to assign ownership to my user account, and have the webserver processes running as my user account, so I can edit files (or remove folders) without worrying about permissions beyond that of the user running the web server process.

(e.g. I can read and write without giving permission to group or world users...)

is it an idea to add a file config.inc.default.php
so that we do not need to make a empty file but just rename this one if its a clean install

I do that currently.

It’s still a hassle. I was thinking that we should just swallow the hassle and put in checks into the installer to check for it first ... hmmm ... there’s gotta be away to make this simpler!

:D

on my server (linux) i am able to do a lot with linux commands in php instead of using the php comands that way I was able to chmod and copy / move files like this:

The system configuration that allows the php script to run as the file’s owner and not as the apache user only works for the CGI installation of php; most mass hosting sites use the apache module, where it will not work.

Quote from: sottwell at Jul 27, 2005, 01:14 PM

The system configuration that allows the php script to run as the file’s owner and not as the apache user only works for the CGI installation of php; most mass hosting sites use the apache module, where it will not work.

Actually, our hosting service, and many shared hosting services, are installing phpSuExec which does this for the Apache module version of PHP (suExec was for the CGI version), and though may take away some flexibility in regards to changing PHP flags in .htaccess files, has added a layer of security to that site that is virtually unbreakable.

I offer hosting accounts featuring this.