myseconddomain.com does have it’s own context, but to make sure I wasn’t having any strange issues I decided to start fresh with a completely new install using a different domain / cpanel account.
after setting up the new domain / account on cpanel everything works great on the installed domain using the default web context. I then setup the myseconddomain.com reference by creating a new account in cpanel and then copied over the config.core.php and the index.php files from the myfirstdomain.com installation.
edited config.core.php file has to point to correct dir
define('MODX_CORE_PATH', '/home/myfirstdomain/public_html/core/');
define('MODX_CONFIG_KEY', 'config');
There is nothing changed in my index.php file, because I used the default web context if I was going to use a different context I would just change
$modx->initialize('myseconddomain');
From here I had to change some base_dir rules and group file access rules to allow files access outside of their root account. Once this is done the myseconddomain.com can view the default web context, but it can’t run any snippets from myseconddomain.com. One thing I did notice is that if I run the web context from myfirstdomain.com and allow it to be cached then myseconddomain.com can also view that cached pull from the snippet, so pulling all static material seems to be fine just can’t get snippets to run.
Again these settings work on rev 2.0.8 and below....Thank you for help
MODX Staff