Process to Update Existing Root Domain MODX Instance with Subdomain MODX Instance

I have a dev version of a Revo 2.2.10 site on a subdomain, and want to get crystal clear about how to 'move' this to the root instance of MODX (same version).

I've soft-launched the site on root, and have dev ongoing on the subdomain, so I'll need to do this a few times.


Here's what I intend to do:

1. Clear cache and sessions on subdomain
2. Export subdomain database
3. Copy root htaccess
4. Export root database for just-in-case
5. Import subdomain database into root
6. Clear root cache
7. Import root htaccess

That should do the trick, right?

8. Run Setup on the root domain.

Quote from: BobRay at Feb 06, 2014, 10:16 PM

8. Run Setup on the root domain.

Thanks Bob. Another MODXer gave me the same direction.

I'm confused by this, though. Why do I need to {re}run setup if MODX already exists there?

Setup detects that there's already a site and treats it like an upgrade or migration.

It updates your database so that it's ready to use with the new file system locations, new [[+site_url]], etc.

The settings in the files will already be correct (assuming that you don't copy any files from the subdomain), but the ones in the DB will be set for the subdomain (e.g., the path in the modx_workspaces table). Setup can't really hurt anything and will straighten out some of the paths in the DB. If you have paths set in Context Settings, you'll have to correct them by hand and extras that set paths in the DB may have to have them corrected. Uninstalling and re-installing the extra may fix that.

I'm not sure about Media Sources. Those may have to be corrected manually.

Quote from: BobRay at Feb 07, 2014, 12:54 AM

The settings in the files will already be correct (assuming that you don't copy any files from the subdomain), but the ones in the DB will be set for the subdomain (e.g., the path in the modx_workspaces table). Setup can't really hurt anything and will straighten out some of the paths in the DB. If you have paths set in Context Settings, you'll have to correct them by hand and extras that set paths in the DB may have to have them corrected. Uninstalling and re-installing the extra may fix that.

I'm not sure about Media Sources. Those may have to be corrected manually.

OK, thanks. This is really helpful. I followed a completely different process with an Evo site and I'm glad to have a more complete approach here.

One final set of questions --- what exactly should I upload to the root directory from the install package? Just the setup directory? The whole package?

you will need all the files from install-package, if you didn't copy them allready with all your other files.
Otherwise the setup-directory should be enough.
And make sure, the uploaded files are the same version as the old installation was!

If possible upload one zipped file and extract them serverside.

Quote from: Bruno17 at Feb 07, 2014, 12:22 PM

you will need all the files from install-package, if you didn't copy them allready with all your other files.
Otherwise the setup-directory should be enough.
And make sure, the uploaded files are the same version as the old installation was!

If possible upload one zipped file and extract them serverside.

Thanks...

I must be asking seriously noob questions, but if I unzip the package in root, and this package contains directories named core, manager, etc., that already exists because it's an existing install, here again, I get a little murky in terms of process.

So, to be clear, you're saying unzip the full install package in root and then run install. Right?

And, thanks for the note about the version. I know 2.2.11 was released but I'm still on 2.2.10. This is not available on the previous versions page and the only other version I can find is called 2.2.10-pl-advanced. I just want to keep this process as simple as possible, and it's evident that the advanced package is different than the norm. Any idea where I can grab the standard version of 2.2.10?

Sorry I don't know. Both traditional and advanced distros or 2.2.11 are available here: http://modx.com/download/release/revolution-2.2.11-pl.

2.2.12 should be out very soon.

You might consider upgrading the subdomain site before the transfer.

Here's the method I use: http://bobsguides.com/modx-upgrade-faq.html

Quote from: BobRay at Feb 07, 2014, 05:09 PM

Sorry I don't know. Both traditional and advanced distros or 2.2.11 are available here: http://modx.com/download/release/revolution-2.2.11-pl.

2.2.12 should be out very soon.

You might consider upgrading the subdomain site before the transfer.

Here's the method I use: http://bobsguides.com/modx-upgrade-faq.html

I just need to run the upgrade. Easiest thing to do.

But, my question remains, again, I'm just unclear on process. I upload the entire install package to root even though there are directories there with identical names? I guess I'm unclear on what happens if I do. I'd assume I'd get a message about the name conflict and to confirm an overwrite?