What do I need to check before EXPORTING the DB?

I’ve changed my troublesome password in the backend using Adminer and now need to re-export the database for the site. I’m lost in the options! Can you please guide me here?

Can you describe in a little more detail what you are trying to do?

I think in the last topic, you were trying to create a new site with an ampersand (&) in the password and then trying to change the password after the site was created. Does that sound right?

To this specific question, if you are wanting to get a sql file with all of the content of the DB, you’d want to check all of those tables to be included in the export.

However, if all you are trying to do is update the password for the site after it has been created, you can do that a couple of different ways which are covered in this FAQ:

Hi Ben,

I’ve since solved the issue. Indeed, I had to import the site and ignore the “failed tables imports”, open Adminer, change the wp_users table row user_pass to a string that doesn’t contain &, put it to md5 type, save the table. Then I exported the local.sql file with everything selected.

I dropped that local.sql in my app/sql and removed all other files. I also reverted to v 5.6.2 which has a lower version of PHP set during Preferred settings, and so the combination of all this allowed me to salvage what I thought might be a lot of work lost. Also seems I had to install Local for “only me” in order for drag/drop to work for import.

It was alot of hours of me hating Local but in the end, I’m happy it was resolved. I learned something and I am definitely never putting & in a password again.

When I finally upload to live site, how do you suggest I change the password to something more secure? Is that something that a migration/duplication plugin would be doing for me or would you advise I just do the same manual procedure I performed here?

This is the best way to learn! :smiley:

You should be able to update that password within the WordPress admin by navigating to your profile after logging in. This should be able to be done even in Local and the new, secure password would be the same after deploying it to the remote server.

The only reason an ampersand can’t be used when creating a new site in Local is that it causes issues when Local is trying to create the new site. For a site that is already installed, changing a password can be done using the normal tools found in the WordPress admin (profile page, forgot password on login page, etc)

1 Like

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.