So, let's go with the assumption that the name you had chosen for your new servername is:
define('HTTP_SERVER', 'http://www.yoursite.com');
define('HTTPS_SERVER', 'https://www.yoursite.com');
your previous/existing servername is:
define('HTTP_SERVER', 'http://www.mysite.com');
define('HTTPS_SERVER', 'https://www.mysite.com');
In both cases you want the site to show as in the root of the above server name so:
define('DIR_WS_CATALOG', '/');
define('DIR_WS_HTTPS_CATALOG', '/');
For the original site (
www.mysite.com) the FS CATALOG might be something like:
define('DIR_FS_CATALOG', '/var/users/webserver/public_html/');
Then you have the yoursite location that is in a subdirectory off of public_html, even though it will be a "different" server, it is still in the same file structure as the mysite location, so the new site would have a file structure of.
define('DIR_FS_CATALOG', '/var/users/webserver/public_html/yoursite/');
So, it is this last part is what I was referring to about having file paths containing the subdirectory.
Although much is missing, the yoursite configure.php file would include/contain.
define('HTTP_SERVER', 'http://www.yoursite.com');
define('HTTPS_SERVER', 'https://www.yoursite.com');
define('DIR_WS_CATALOG', '/');
define('DIR_WS_HTTPS_CATALOG', '/');
define('DIR_FS_CATALOG', '/var/users/webserver/public_html/yoursite/');
The mysite configure.php would be like:
define('HTTP_SERVER', 'http://www.mysite.com');
define('HTTPS_SERVER', 'https://www.mysite.com');
define('DIR_WS_CATALOG', '/');
define('DIR_WS_HTTPS_CATALOG', '/');
define('DIR_FS_CATALOG', '/var/users/webserver/public_html/');
Bookmarks