I have installed the system and installed the claritypack template, but my site doesn’t render any html when accessing the site. No errors, no html nothing but a blank screen. Nothing in the error logs either.
Any ideas?
I narrowed it down to this line:
@include(’config.core.php’);
If I comment that line the page will render. Why is that?
That should be:
@include(dirname(__FILE__) . '/config.core.php');
It’s possible that one or more of your config.core.php files didn’t get set properly during the install (you did run Setup, right? -- it’s not enough to just install the files).
Commenting out that line sets the core location to the default (/core), which suggests that including that file sets it wrong. Take a look in the config.core.php file in the root and see what it’s setting the core path to.
There are three other config.core.php files as well. You should check them all:
§ MODx root directory
§ /manager/
§ /connectors/
§ /setup/includes/
OK. I tried a new install on a completely different server (my own) and got the same results. If I comment out the line below - it works, otherwise - nothing is rendered.
//@include(dirname(__FILE__) . ’/config.core.php’);
I checked the error_log and nothing is reported , I also checked the other config.core.php files and here is what I got:
setup folder - No file present
manager folder:
<?php
define(’MODX_CORE_PATH’, dirname(dirname(__FILE__)) . ’/core/’);
define(’MODX_CONFIG_KEY’, ’config’);
connectors folder:
<?php
define(’MODX_CORE_PATH’, dirname(dirname(__FILE__)) . ’/core/’);
define(’MODX_CONFIG_KEY’, ’config’);
setup/includes folder
<?php
define (’MODX_CORE_PATH’, MODX_INSTALL_PATH . ’core/’);
define (’MODX_CONFIG_KEY’, ’config’);
define (’MODX_SETUP_KEY’, ’@traditional’);
As far as looking at the config.core.php file in the root, that is not possible. The file is encoded and cannot be read. When I did the install on the other server - I got the same results. One thing I noticed that don’t look right to me is that the other three config.core.php files are missing the ending ?> tag. I did try adding the ending tag to the files in the manager and connectors folders but it made no difference.
Any ideas?
-
☆ A M B ☆
- 24,524 Posts
Ending ?> tags are not a requirement of PHP; many veteran coders deliberately leave it off to help prevent the errors that having extra whitespace after the tag will cause.
As far as looking at the config.core.php file in the root, that is not possible. The file is encoded and cannot be read.
Any ideas?
Encoded? MODx doesn’t encode this file -- did you?
-
☆ A M B ☆
- 24,524 Posts
He may have one of the code encrypters set up; my new hosting (Bluehost) offers two of them. I made sure both of them were disabled.