I have moved my site over to a staging environment, and then updated to V6B4. I have a “Single” Layout, which is completely empty after the upgrade. No other changes were made, just the theme upgrade.
With 5.1.5:
After upgrade to V6B4:
Thanks for testing! We’ll see what’s going on.
Hey Striata, Did you spin up the new site with the wordpress importer? If you can, does importing from a DB dump fix this issue? I’m seeing some weird encoding from the JSON on that page relating to custom HTML in some of your elements. Specifically the modal and timegraph. I’m not sure how much we’ll be able to do if this is an importer exporter error, but we’re looking into this and seeing what we can can at the decoding level. Thanks.
This has been done with the “staging” function of Cloudways. Pull the live site over to staging, then running the update to the beta 4 there.
I could stage the live site again, without doing the update. Then you can have a look at the “strange things” (if something weird has already happened), and then run the update yourself on the staging site.
Shall I do that?
Okay thanks for the info. Yeah try to stage again and we can see if a migration did something wrong. A DB dump of the live site would help too, I’ve gotten a couple of WP importer issues which is why I try not to rely on that.
Hi @charlie, I have just staged the live site again. Fell free to poke around the staging site and update it to v6.
Don’t know how to do a DB dump. Can you enlighten me?
Hey thanks I’ll take a look this week. Looks like we can cross off DB migration if the layout is still there on staging pro 5.
A DB dump refers to doing something like mysqldump DB_NAME > db_file.sql however I don’t recommend doing that for me unless you know what you are doing. In this instance we don’t need to do that too.