We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 9496
    • 113 Posts
    So Im doing my first big site with Revo 2.1.1 Got everything running smoothly with multiple contexts from one installation. The only problem I am having is with one site that is on a different server from the core install (the core is media temple, the other is earthlink). I have the three hosted on the same server working great. I simply placed the config, htaccess and index.php and it points to where it needs to go. Now for the remaining its on an entirely different server so the modx_config_path definition in the config file naturally doesn’t resolve.

    I didnt want to have to switch server hosts at this time for my client (its currently earthlink) since Im only dealing with the web front end.

    So as it stands my core install path is:

    define('MODX_CORE_PATH', '/home/xxxx/domains/my-site-name.com/html/core/');


    and I thought that I would just need to replace it with something like:

    define('MODX_CORE_PATH', 'http://my-site-name.com/core/');


    but that doesn’t seem to do the trick. I also thought that I could simply alter the DNS "a" records to point to the new host IP, which obviously would work but Id have to contact customer support at Earthlink (no joy there) so its kind of the last resort. Anyone have any ideas of how to structure the config path (or if its even possible?)
    thanks in advance -
    P
      • 24068
      • 4 Posts
      Its imposible as some files under ’MODX_CORE_PATH’ must be writeable. http-protocol is not.

      Rember:

      * Pretty much everthing in modx that is a "path" must be a local filesystem path, and mostly writeable by modx
      * Pretty much everthing in modx that is a "url" must be remote path and normaly starts with http or https

      Again, as i posted allready in another topic: Just because phps "include" function can include http-url, does not mean that you should do it or asume that its OK to do it. Its just plain wrong. There are no excuses to do it. The day the php-team decided to allow for this by default was a very very bad day for security.

        • 9496
        • 113 Posts
        Pureppl

        Thanks for clarifying. Like I said, I can reroute the A records to point to the core host IP but Im required to go through a customer service hassle which I really didnt want to have to worry about, or probably switch hosts entirely anyway. But whether or not http-url on php includes is good or bad I won’t even speculate...
        P