We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 51382
    • 53 Posts
    Short story, short. Being a newb in everything technical, I migrated my dev environment to production, not realizing it's not as simple copying the files.

    Now both environments control production.

    Is there an easy way to disassociate test.testurl.com from myurl.com, so dev cannot control production, or should I just take the site offline and follow the instructions that I have since found?
      • 18373 ☆ A M B ☆
      • 3,141 Posts
      That sounds interesting - how did you get both environments to control production? laugh

      I'm guessing you might just need to create a separate database for dev and production, and update the config files in core/config/ to point to the right ones.
        Mark Hamstra • Developer spending his days working on Premium Extras and a MODX Site Dashboard with the ability to remotely upgrade MODX and extras to make the MODX world a little better.

        Tweet me @mark_hamstra, check my infrequent blog at markhamstra.com, my slightly more frequent ramblings at MODX.today or see code at Github.
        • 51382
        • 53 Posts
        I have absolutely no idea since there is no mention of the actual urls anywhere except css & js references.

        And thanks, I will try that.
          • 51382
          • 53 Posts
          Editing the config file is leading to a 500 error when I try to crate new resources under the production url.

          I think I will need to go back and follow the proper steps.