I’m using Local Beta (up-to-date) because I googled this exact problem and the solution on the forum was to use the Beta. However that’s not working for me as I continuously get “Local couldn’t load the file list!”
What steps can be taken to replicate the issue? Feel free to include screenshots, videos, etc
Start site and push (production, also MagicSync is on)
Local does a pretty good job of scrubbing private info from the logs and the errors it produces, however there’s always the possibility that something private can come through. Because these are public forums, always review the screenshots you are sharing to make sure there isn’t private info like passwords being displayed.
You’ll need to find the database file for your exported site, and you’ll put that database file where you put the wp-content in the new Local site you made. Then you can run the import command in terminal for the database.
Any folders for WP Optimize would be specific to that plugin if you’ve used it lately or in the past. So it might not be a recent backup of the database. Your WPE backup should just have a regular SQL file, I think it might be inside of the WP Content folder itself. That will be your database backup from WPE. You’ll just want to move that out and put it in the root.
@cnguyen Yes that mysql.sql file will be your database. You’ll want to move that into the Public folder, and then you can run the command wp db import mysql.sql to get it imported. Once that’s done you’ll do a S/R to clean up the domains.
I think what you might be running into now is a bug between Windows/WPCLI/PHP8.
If you create a site with PHP 7 you might be able to import there.
Going back to the original backup zip though. I had a thought that maybe you could try honing the zip file down to just the necessary WP-Content and SQL files. Could you remove any core files, WP-Optimize directories, backups, etc and then zip the file up again?
Successfully pushed the honed production ZIP version to Staging. The website looks funky, naked, and from the 90s, but it works! The final steps for testing MySQL8 compatibility is pushing Staging to Production, though, I’m not going to do that for obvious reasons.
Is the push to Staging more than enough as a test that the upcoming 9/27 update will be fine for our production site?