Setup doesn't seem to set paths when core is moved out of webroot tree

I am embarking on my first ModX project and am impressed and excited.

I have installed and reinstalled modx multiple times now on my development machine - but now when I move the core directory outside of my webroot path and successfully run setup - I get errors when I run the manager. It seems to be trying to access core in my webroot where I installed modx.

I copied core into /var/www/sitefiles/xtest: /var/www/sitefiles/xtest/core/

I put all the other files into my web tree at: /var/www/html/xtest

I created all the directories and set permissions in the install directory and core directory as per instructions. As a final step I set the permission to 666 for setup/includes/config.core.php.

I run setup successfully, entering the absolute path for core when prompted.

Then when I try to run manager, I get the following php output:

Warning: include_once(/var/www/html/xtest/core/model/modx/modx.class.php) [function.include-once]: failed to open stream: No such file or directory in /var/www/html/xtest/manager/index.php on line 47

Warning: include_once() [function.include]: Failed opening ’/var/www/html/xtest/core/model/modx/modx.class.php’ for inclusion (include_path=’.:/usr/share/pear:/usr/share/php’) in /var/www/html/xtest/manager/index.php on line 47

Warning: include(/var/www/html/xtest/core/error/unavailable.include.php) [function.include]: failed to open stream: No such file or directory in /var/www/html/xtest/manager/index.php on line 48

Warning: include() [function.include]: Failed opening ’/var/www/html/xtest/core/error/unavailable.include.php’ for inclusion (include_path=’.:/usr/share/pear:/usr/share/php’) in /var/www/html/xtest/manager/index.php on line 48
Site temporarily unavailable!



This is for
modx-2.0.5-pl
CentOS 4.7
PHP 5.2.14
MySQL 5.1.50

Whats in your config.core.php file?

I assume you are using the advanced distribution? Advanced is the only distribution that supports relocating the core and other file locations automatically in setup.

Thank you OpenGeek. I completely overlooked that!