Changing package path in moved MODx installation

I moved a site from a local server to a remote server.

Local site path: /var/www/mysite
Remote address: /home/mysite/public_html/

After editing /core/config/config.core.php appropriately, fixing file permissions and clearing the cache, I got everything working fine.

Until, that is, I tried to install a package - formit, as it happens. It downloaded successfully (and I can see it in /core/packages) but here is what I get if I try to install it:



There is no issue with permissions; as you can see, the old path is still in there somewhere and messing everything up. However I have checked and rechecked /core/config/config.core.php and there is no path problem there.

Any suggestions would be greatly appreciated.

You need to edit the modx_workspaces table and modify the path field in the "Default MODx workspace" record in that table. Running upgrade after moving a site should resolve this and any other path issues, for future reference.

I know this is a really silly question, but exactly what do you mean when you say "run upgrade"? I’m not familiar with that.

Thanks!

Run the installer and select "Upgrade" (it should already be selected). You’ll probably need to upload the install folder from your original unzipped package.

Thanks, both. I have been hacking my way through migrations but will start doing it "right" from now on