db tables import error – duplicate primary key

We generally don’t recommend copying the wordfence tables and data over. Export your settings at the bottom of the options page on the old site and import them into the new site in a clean wordfence installation. This brings over blocked IPs and most everything.
So export settings, check options to delete tables and data on deactivation on the old site, deactivate and delete wordfence on old site, take sql dump, import sql dump into new site, install new wordfence, import settings.

tim

Oy! This is what I was looking for, though I might have also been looking for better news :). It all makes plenty of sense.

What about the same operation in reverse – i.e. I want to periodically update the dev site to be a nice copy of the actual production site. In that case, I’m not ever looking to delete WF from the production site. Can I simply remove the wp_wf* tables from the SQL database before importing the exported SQL database?

@iananewton: That might work in your situation on the dev site. You might also want to use the option “Disable config caching” on the dev site, so when the config table is imported, it’s not out of sync with the cache. (Make sure also that you have the same version of Wordfence on both sites before copying the tables over.)

If you have more questions on this, can you create a new post? This helps us keep track of open issues better, and keep in line with the www.remarpro.com forum rules. Thanks!

-Matt