Urgent - No content showing after switching from dev url to main url

Hi

I have just switched my site url from a dev url to a live url (same server and setup) and now I have no BB content showing on any pages. When I try to edit a page the BB content shows up but it’s all a mess. I have cleared the cache in the plugin settings as well as the cache on my web host. Any ideas on what’s happening?

Thanks.

Hey Greg,

Sorry to hear you’re having this problem. Do you mind listing the steps you did when you migrated the site? Please check the link below for more info on migrating BB sites. :slight_smile:

http://forum.wpbeaverbuilder.com/knowledge-base/migrating-a-site-to-another-domain/

Thanks!

KC

[Content Hidden]

Sorry to but in - hopefully this is of some help!
I have been a user of BackupBuddy for a while, but on 2 or 3 occasions I have tried using the method in the thread that KC has linked to above.
My experiences have been (on at least 2 occassions) that all works OK, except (and a big except) the entries in the options table for the URL and the Site Address don’t get updated.
So I have had to use phpMyAdmin to manually changes them (and refresh the .htaccess via permalinks in the WP-Admin - something I do as a matter of course), then the site is all good.
I would welcome others experiences?
Cheers, Dave

Hi KC. I ran the search and replace, cleared the cache (and my server cache) but I’m still seeing no content. Any other ideas?

Aside from the url change from dev to live, there was a change in url afterwards from http to https. Would that affect BB content not showing up?

Hey Greg,

How did you do the migration? Did you do it manually, i.e., copying the files via FTP and exporting/importing the DB? Or does your hosting offer a staging to live migration? Do you still have a backup of the old DB?

BB stores data in a serialized array. Chances are, the serialization broke causing the problem you’re having now.

I’d suggest exporting the staging DB, import it to the new server, then run the Serialized Search and Replace script mentioned above. Let us know how it goes!

Ben

[Content Hidden]

Hey Greg,

The site being http or https shouldn’t matter. I’m assuming it’s safe to restore the DB prior to doing the search/replace? If you do so, and change the URLs back, does the site work?

Do you mind listing down the steps you did when you changed the URL up to this point? Could you also share the dev and live URLs?

Ben

[Content Hidden]

Hey Greg,

So before doing step 5 was when you made a backup of the DB? And just to be sure, you searched for http://s14394.p284.sites.pressdns.com, with the http, and replaced it with https://www.traffika.com.au, with the https?

Do you mind sharing temp admin access to the site? I’d like to check the DB.

Ben

[Content Hidden]

Hey Greg,

You can just use a dummy email and post the access details here using private reply.

Ben

[Content Hidden]

Hey Greg,

I just checked the homepage postmeta table on the DB and there are indeed broken serializations. That is actually pretty complicated, if not impossible, to fix.

I would suggest importing the backup DB from before you ran the serialized search and replace. Just to verify, you did use the script found on the link above? And when you ran it, did you run it on all the tables? Could you rerun the script after loading the backup and this time search for s14394.p284.sites.pressdns.com and replace it with www.traffika.com.au?

Ben

Thanks. I reverted back to before I ran the search / replace but no luck. Do you have any further insight into what might have happened? I’m working with Pagely support but they have asked

Hey Greg,

I just checked the DB again and the same problem is there. Are you using the script we recommended above? Also, do you think you can send me a copy of that backup DB? Or probably just Dropbox it.

Ben

[Content Hidden]

Hey Greg,

Hopefully, we can avoid that. I’m just going to check if on that backup DB the serialization is still intact. If so, we can avoid having you restore to a much earlier backup.

I just checked your previous reply. Sorry, I just have to ask. Did you simply restore the DB? Or did you run the script after restoring it?

Ben

[Content Hidden]