Check the path in the workspaces table. Although that may not be wrong and the packages will remain broken.
Something is preventing the workspaces table path from working properly, once moved. Workspaces table should have {{core_path}} set, and usually does when checked. This should work fine, and normally does. It just doesn't seem to after a move.
I can't find the recent threads that discussed this/similar issue but I've run into it the last 3 times I moved a site. My work around is to pull all the transport.zip files out of the core/packages folder, and re-upload them all. It tends to reset how MODX validates that the transport.zip files exist in the directory that they actually exist in. (core/packages)
Now, I did it one by one by running the uninstaller till it wouldn't uninstall anymore (package typically remains), attempting a remove, and then manually deleting the transport.zip file. If remove doesn't work, just delete the transport.zip anyway. Then, download a new copy from package management and reinstall. This would be the more time consuming way to resolve it, however. I recall someone else had a better/faster solution.
When you moved to the new server, did you reinstall MODX? If not, or... even if you did. Try that. Make sure not to use FTP, but upload a new .zip file to the server, and unpack it on the server itself (control panel or extract tool). Then re-run setup, like an upgrade.
-
- 97 Posts
So, the problem was MySQL Version. After updete to 5.5.30 everything works as it should.