broke website

Hi csleh,

I am sorry for the inconvenience.
Do you mind reaching out to me at support at servmask.com, so I can have an engineer investigate your case further?

I believe the problem was mainly that the admin email was changed — the same username was used on both old and import site but neither had the email address it changed to.

Then the new theme had a problem and I couldn’t get a password reset because of the incorrect email.
After I was able to set up a new admin in mysql I could get back in, and found that import/rewrite had worked.

Thank you for the update, csleh.
Has your site been migrated successfully and properly?

I don’t know. The posts/pages/media moved and the advanced custom fields are all in place. It looks like some other info in database is untouched (like form fields) but some is suddenly gone (like an add-on to those form fields).

Now the visual editor and extended toolbar are gone. I don’t know what’s related to moving or something else.

The development server is not windows but the new server is. I’m suspecting something is funny on this windows server and that may be the root of all issues, including the database mess up on migration–although the user email changing doesn’t make sense for any issue.

If you would like the engineer to take a look further, please feel free to reach out to us at support at servmask.com

Always happy to help!
Pim

I forgot to mark this as resolved. I still don’t know why the database borked or the admin email changed, but the other problems were fixed when I added a new admin and used that profile.

So except for noting that quick access to the database in case of lockout is a good idea, I would recommend this plugin for when replacement of everything is preferable to regular import. I’m especially impressed with your responses here and attempts to help. Thank you!

Thank you for your kind words, csleh and for being our user!

You may try importing the .wpress file (that has problem with the changed admin email) on your localhost and see if the issue persists.
I am guessing the problem is actually from your exported site.