Newbie Frustration / New MODX

15 Posts

mferry Reply #11, 5 years, 8 months ago

UPDATE.... I moved core back to be under my web root.
Updated all the paths... The manager and website works fine !!!! No issues.

When I move it outside the document root.... change the paths it breaks the INCLUDES.

15 Posts

mferry Reply #12, 5 years, 8 months ago

Folks,
I think I have this resolved.

OLD: define('MODX_CORE_PATH', dirname(__FILE__) . '/var/www/sites/blah.com/core/');
NEW: define('MODX_CORE_PATH', '/var/www/sites/blah.com/core/');

Like I had advised the system was appending my full path of my core to the webroot.
When I remove the dirname(__FILE__) or dirname(__DIR__) it doesn't append it. Setting my core path to just the path set in the second variable(Only variable in the define).

The manager page does load now.

1,154 Posts

nuan88 Reply #13, 5 years, 8 months ago

Right right that should be the difference between relative and absolute paths.

Quote from: mferry at Aug 17, 2018, 04:57 PM

Folks,
Like I had advised the system was appending my full path of my core to the webroot.
When I remove the dirname(__FILE__) or dirname(__DIR__) it doesn't append it. Setting my core path to just the path set in the second variable(Only variable in the define).

Now make sure you have the right code in the template <head>, not sure if you have this stuff handy or not

<html lang="[[++cultureKey]]" class="no-js">
<head>
<title>[[*pagetitle]] | [[++site_name]]</title>
<base href="[[!++site_url]]" />
<meta name="rating" content="" >
<meta name="author" content="">
<meta name="keywords" content="" />
<meta name="description" content="[[*description]]" />
<meta name="robots" content="index, follow">

<meta name="viewport" content="width=device-width, initial-scale=1.0" />

<meta http-equiv="X-UA-Compatible" content="IE=edge">

15 Posts

mferry Reply #14, 5 years, 8 months ago

As far as I can tell... The manager is working fine, but...
when you access the main page. http://blah.com

Error 503

Site temporarily unavailable

nothing is getting in to the log file.
Is there a cache I need to delete?

1,154 Posts

nuan88 Reply #15, 5 years, 8 months ago

yes, in core/cache

discuss.answer

24,544 Posts

BobRay Reply #16, 5 years, 8 months ago

With the moved core, you want exactly this in the first line of the config.core.php files (as you have above) and it should also be the first thing in config.inc.php:

define('MODX_CORE_PATH', '/var/www/sites/blah.com/core/');

You need it there, even though it's defined in config.core.php because sometimes a script might go directly to the config.inc.php file.

MODX uses the config.core.php files just to find the config.inc.php file. Once it finds config.inc.php, it gets all the other locations from there.

Remember that when you move the core, you also move the connectors and processors directories because they're under the core. So these would make sense with your moved core:

define('MODX_CONNECTORS_PATH', '/var/www/sites/blah.com/core/connectors/');
define('MODX_PROCESSORS_PATH', '/var/www/sites/blah.com/core/model/modx/processors/');

Setup tends to daisy chain the settings like this:

define('MODX_CONNECTORS_PATH', $corePath .  'connectors/');

But on some servers, you need to hard code each path on its own.

Did I help you? Buy me a beer
Get my Book: MODX:The Official Guide
MODX info for everyone: http://bobsguides.com/modx.html
My MODX Extras
Bob's Guides is now hosted at A2 MODX Hosting

1,154 Posts

nuan88 Reply #17, 5 years, 8 months ago

That's pretty clear Bob, thanks for laying it out so nicely

MODX uses the config.core.php files just to find the config.inc.php file. Once it finds config.inc.php, it gets all the other locations from there.

And thusly, wine was invented. Or the need for wine, which is almost the same thing

Answered Newbie Frustration / New MODX