Okay, I figured this out on my own, but it was a huge hassle.
First, my situation might be a bit unique. I decided to drop my blog back in November, but then had a change of heart (and server) in March. I installed WordPress on the new server and this plug in, hoping I could just restore the webpage from the file that I’d saved on my dropbox. Instead, I got the error noted above.
To fix the problem, I created a new backup of the basically empty page. I then took all the files from the old backup (under the pressback subdirectory) and saved them in the new backup EXCEPT the “server” file. This then allowed me to restore nearly all the files.
Unfortunately, my new install of WordPress decided to use different table names on the database. For example, my posts were in a table called ‘wp_posts,’ but the new install decided to call them ‘wp_xyder_posts,’ (totally made up the exact name, but it was something like that). So I went into the database.sql file found in the old backup, copied the text to notepad++, did a find/replace to replace all the ‘wp_’ with ‘wp_xyder_’.
Finally, I jumped into MySQL, dropped all the tables (got an error just trying to override them), copied the new text into the “SQL” box in MySQL, and ran the SQL script. I logged back into my WordPress Admin, refreshed the database, and all my posts were back up.
It’s still not 100% like it was before, and I imagine I’ll have to do a bit of tweaking to get it there, but at least all my posts, pictures, plugins, and themes are in place.
Likely there was an easier way to get this to work, but at least it works.
