Move core directory after install (ModX Revolution)

Part of the reason for isolating the sites this way, rather than using contexts, is that the site owners may wish to move their sites. That means I need an easy way to package up a single site and move it to a new hosting provider. What I am currently doing is hosting a couple of web sites for non-profit organizations in Costa Rica (where I lived most of the year for 8 years after retiring and before moving back to Canada just over a year ago). I won’t be having those sites piggy-backed on my hosting account forever!

By the way, I do use shared hosting and don’t have SSH, though I believe I can do everything necessary to complete an advanced install.

Thank you very much for the warning about keeping the assets/components and core/components in sync. I would tend to do this as I like to keep all the sites on the same "release". I am currently aiming at converting three sites to MODx:

- My own site (mainly used for experimenting) and currently using Joomla! (and Gallery3 and TNG genealogy software)
- The Women’s club of Costa Rica (WCCR), currently totally hand-coded (and hence the easiest for me to convert and the first I am working on)
- The Little Theatre Group of Costa Rica (LTG), currently using Sandvox with a lot of hand coding.

I had wondered about "workspaces" as I had not seen any documentation about them.

Thank you also for spending the time that you do on the forums. I’m sure all the MODx users who visit the forums appreciate you help and advice.

My next two steps in the learning process involve:

- Learning how to apply the security model to restrict what various users can do (and/or access). I’ve got "Login" up and running alright.
- Learning how to create a simple content-updating environment for volunteers in the the two organizations I mentioned to manage the content themselves.

Quote from: jrg at Dec 20, 2010, 09:21 PM

I had wondered about "workspaces" as I had not seen any documentation about them.

They were an original idea of having different configurations of installed Packages for different sites (or multiple configs for single sites). However, they were ultimately postponed development, as their complexity prohibited them from coming into 2.0. Since then, we’ve been unsure if that route is an appropriate and/or useful route of package distribution and management workflow for a server.

Just another one that users may want to check is any namespace settings that you have set up. If for instance you have developed any CMP addons and extensions to the framework - following something like the doodles tutorial - then you may have set up a namespace for that which points to the core directory. If you have, double check these as part of the move the core directory (and change them to the {core_path} anyway)