We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 32678
    • 290 Posts
    I’ve completed development on one project within my dev environment and need to begin a new one. What is the correct procedure for replacing the existing site and database with a new one?
      • 18373 ☆ A M B ☆
      • 3,141 Posts
      I usually make sub folders for different projects, each with its own MODx install and database.

      If you want to stick with a single dev project at a time, back up all your files and the database (you might want it later) and wipe the whole thing. Install MODx again with a new database (or a different table prefix) and start with a clean slate!
        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.
        • 28042 ☆ A M B ☆
        • 24,524 Posts
        Same here; I usually have half a dozen projects going at once, so I’ll have each one installed in its own subdirectory. Every now and then I go through and zip for archive purposes then delete the ones I’m not working with any more. To be honest, in the four years or so I’ve been doing this I’ve never once had any use for the archived project!
          Studying MODX in the desert - http://sottwell.com
          Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
          Join the Slack Community - http://modx.org
          • 18373 ☆ A M B ☆
          • 3,141 Posts
          One of our clients once managed to remove all files of a (non-MODx) rss feed integration in some sort of handbook he published. Gotta love backups in cases like that.
            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.
            • 28042 ☆ A M B ☆
            • 24,524 Posts
            Oh, I have backups of all the final live implementations, and the ones I’m still supporting get updated regularly and used from time to time. It’s just the final development archives that are lurking in the dark corners of my hard drive (and on a USB storage device as well).
              Studying MODX in the desert - http://sottwell.com
              Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
              Join the Slack Community - http://modx.org
              • 32678
              • 290 Posts
              Cool -- thanks. I set up a sub-folder and after wrangling XAMPP, this works like a charm. I had to change permissions on the XAMPP directory, which was a pain because I was not part of the root admin group on my iMac. Sigh -- gotta love Google. After renaming and configuring .htaccess per the FERL guide provided by MODx (http://wiki.modxcms.com/index.php/Friendly_URLs_Guide), and changing permissions in httpd.conf, all works well. Probably makes sense to keep master copies of .htaccess and httpd.conf to overwrite existing files with in new installs.