Dual Installation Query

Heya,

I have an existing site which utilizes the evo version of Modx.

For just over 18 months I've been experimenting with Revo and have built a few sites using it.

I have an interest in re-developing the evo site using Revo from the ground up, simply for the sake of practice and repetition to lodge techniques into my head.

I would like to install the Revo package on the same domain server space as the Evo site. Naturally I suspect the Revo will have to reside in a sub-folder.

When the Revo site is complete, I would like opinions on the best practices for disabling the old Evo site and ensuring that resources on my Revo appear at the root domain level (not a subfolder).

Thanks

You can definitely put Revo in a subfolder. When it's working, one method is to back up and delete the Evo site, copy the Revo site to the web root, and run Setup to straighten out the paths.

You will need to use a different database or a different table prefix for the Revo site.

Another option is to install a local web server like XAMPP and develop the Revo site on your local machine, then move it to the remote server.



------------------------------------------------------------------------------------------
PLEASE, PLEASE specify the version of MODX you are using.
MODX info for everyone: http://bobsguides.com/modx.html

When I'm doing something like that, I prefer to rename the root files and folders of the new installation by simply adding .new to them, move them into place, then rename the original files and folders by adding .old to them, and finally rename the new ones by removing the .new.

This way if something goes horribly wrong all I have to do is rename the new ones by adding .new to them, and rename the old ones by removing the .old and it's back running as it was originally.

Then I can just zip up all the .old stuff to keep a copy of it in a backup somewhere and get it off the server once I'm sure the new one is working properly; usually after a couple of weeks or a month.

That sounds like a great method. Just to be clear, you're renaming the manager, core, assets, connectors, and index.php?


------------------------------------------------------------------------------------------
PLEASE, PLEASE specify the version of MODX you are using.
MODX info for everyone: http://bobsguides.com/modx.html

I rename all MODx-related files and folders in the root. That way they won't conflict with the new ones I'm moving in. It also means your site is only down for the amount of time it takes to rename the ones you want to be using.

Excellent,

Certainly seems the most logical method, and time efficient. I shall comment back when it's done.

Thanking you two