Migration to New Domain Unsuccessful

Yani, thank you for your swift reply! Originally, I did not use the find/replace feature…but after several attempts and still not having success, I decided I needed to try it as an option. I will try again without using it.

I do, in fact, use the Wordfence Security plugin – it is installed on both sites I’m working with. I will disable and try again.

Again, thanks and I will update my progress here. (Maybe, this is not quite yet ‘resolved?’)

• This reply was modified 6 years, 8 months ago by traffiquejam.

Any other thoughts/suggestions?

OK, since I don’t really know what I’m doing, I’m copying/pasting the debug information I obtained for you below. First, I installed the plugin “Debug Bar” on both sites. Next, I edited the wp-config.php file for both sites within cPanel (define(‘WP_DEBUG’, true); Since I didn’t know whether to debug the export or the import, I did both. One more thing: when preparing the All-in-One WP Migration plugin for the export, I chose (in the advanced settings) NOT to export the theme files (since I already have the theme set up on the new site), the must-use plugin files, or the plugin files. This also greatly reduced the size of the export file from 140mb to 50mb.

Here is the returned debug info from the export site, post-export:
Cache Hits: 896
Cache Misses: 116

Group: options – ( 164.32k )
Group: default – ( 0.03k )
Group: themes – ( 0.60k )
Group: users – ( 0.37k )
Group: userlogins – ( 0.03k )
Group: useremail – ( 0.04k )
Group: userslugs – ( 0.03k )
Group: user_meta – ( 2.85k )
Group: plugins – ( 10.70k )
Group: counts – ( 0.17k )

Here is the info on the importing site, post-import:
Cache Hits: 900
Cache Misses: 116

Group: options – ( 164.97k )
Group: default – ( 0.03k )
Group: themes – ( 0.60k )
Group: users – ( 0.37k )
Group: userlogins – ( 0.03k )
Group: useremail – ( 0.04k )
Group: userslugs – ( 0.03k )
Group: user_meta – ( 3.15k )
Group: plugins – ( 11.36k )
Group: counts – ( 0.17k )

And finally, here is the debug info on the importing site, post-export and post-permalinks save:
Cache Hits: 998
Cache Misses: 116

Group: options – ( 164.51k )
Group: default – ( 0.03k )
Group: themes – ( 0.60k )
Group: users – ( 0.37k )
Group: userlogins – ( 0.03k )
Group: useremail – ( 0.04k )
Group: userslugs – ( 0.03k )
Group: user_meta – ( 3.15k )
Group: plugins – ( 11.36k )
Group: counts – ( 0.17k )

The bottom line here is after doing all that, the same result occurs: I still can’t get past the big “SORRY” message. Note that this page DOES appear under the new URL, not the old, so it appears the migration plugin is doing its job of making those changes.

One side note: when attempting to go to the home page of the new site, the extension added to the main URL is /cgi-sys/defaultwebpage.cgi . So, I thought about what might happen if I actually entered the URL and then manually typed in a page that exists on the site (say, for example, the /about-us page or the /subscribe page. In every instance, the sites header presented but then beneath it, I got a 404 every time. Does that tell you anything?

So sorry for this being lengthy but I felt it would be helpful to you if I included as much detail as possible in order to help paint the picture of what might be the culprit. I appreciate you not only taking the time to wade through it all but to offer your input via your replies.

Thank you!