Moving site to new Hosting (GoDaddy to GoDaddy)

Hi All,

I am trying to move a Modx Rev 2.2.8 website from one GoDaddy Server to another one. I followed the directions here ...
http://rtfm.modx.com/revolution/2.x/administering-your-site/moving-your-site-to-a-new-server
... but I just get "Error 503 Site temporarily unavailable" on the index.php and "Site temporarily unavailable!" in the /manager/.

I was on the phone with GoDaddy tech support for 2 or 3 hours trying to figure out whats wrong. Does anyone here have any suggestions?

Did you try to re install the modx and import your backup database?

I would install a new copy of the same version of MODX on the new server; make sure to use the same Manager login as you have on the original. Once you're sure it's working as expected, then import the original database and files from assets/ and core/components and core/packages - you could actually install all of the add-ons you're using in the new installation via Package Manager and unless you have custom stuff in the core/components and core/packages directories they would be all set already as well.

You can also use Vapor to package the original site, install a new one on the new server, and install the Vapor package with Package Manager. Just follow the first section of the instructions, get the package from the core/packages directory and upload it to your new site's core/packages and install using the "from local" option in Package Manager.

GoDaddy is notoriously troublesome for MODX sites. As long as you're moving, why not go to a MODX-friendly host?

http://bobsguides.com/modx-friendly-hosts.html

Quote from: alyainec at Jan 29, 2014, 07:37 PM

Did you try to re install the modx and import your backup database?

Okay.
I re-installed Modx Rev 2.2.8.
Then imported the database. I see no resources.
Then I install all the Packages ... WayFinder, VersionX, TinyMCE, spiefeed, mxCalendar, MIGX, getResources, and fastFind.
I still see no resources in the Manager.
Any suggestions?

Quote from: sottwell at Jan 29, 2014, 10:56 PM

I would install a new copy of the same version of MODX on the new server; make sure to use the same Manager login as you have on the original. Once you're sure it's working as expected, then import the original database and files from assets/ and core/components and core/packages - you could actually install all of the add-ons you're using in the new installation via Package Manager and unless you have custom stuff in the core/components and core/packages directories they would be all set already as well.

You can also use Vapor to package the original site, install a new one on the new server, and install the Vapor package with Package Manager. Just follow the first section of the instructions, get the package from the core/packages directory and upload it to your new site's core/packages and install using the "from local" option in Package Manager.

Hi Sottwell,

I did as you suggested, still no resources. I did not use the same manager login as the original, tho. Should I remove everything and start over?

Quote from: BobRay at Jan 30, 2014, 02:30 AM

GoDaddy is notoriously troublesome for MODX sites. As long as you're moving, why not go to a MODX-friendly host?

http://bobsguides.com/modx-friendly-hosts.html

I am having nightmares about GoDaddy, seriously. I think you're right.

you should see resources as soon, as you've imported the modx_site_content - table (there are more tables involved, but this is the one which holds all resources and does build the resource-tree)
make sure, to clear the core/cache/ - directory completly

if you still can't see any resources, there went something wrong.

you normally really just need to import all files from core/components + assets/components and any custom-directories and recreate the database.

Thank you all for your help. The issue was resolved.

The issue was when I imported the database it came in with "mod_" prefixes for all the tables, and the installation had "modx_" tables. Bruno was able to spot the issue and rename the path prefix in the config.inc.php file.

Dan