• Resolved jstallard

    (@jstallard)


    Hi

    I’m running a lot of site transfers at the moment, and there are some issues with Wordfence.

    Home directory names are hard-coded in .user.ini and wordfence-waf.php. Could these reference environment variables instead? Other plugins seem to transfer without difficulty. If I have a transfer problem, it’s usually related to Wordfence. It’s a great plugin, so would be really good if you’d fix it.

    I’ve had a few problems with the wfHoover table, which stop me exporting the database. The error is:
    ‘wfhoover’ doesn’t exist when using LOCK TABLES
    I can get around this with mysqldump or wp db export, but not with wp mu-migration export
    Anyway, database optimize doesn’t fix it. Neither does deactivating and reactivating Wordfence, unless you drop the tables. Can you write a fix into Wordfence Assistant, and maybe add a fix to Wordfence itself, so that it tidies this up?

    Thanks
    Jackie

    • This topic was modified 4 years, 2 months ago by jstallard.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support WFAdam

    (@wfadam)

    Hello @jstallard and thanks for reaching out to us!

    Unfortunately, the codes in user.ini other files, are paths made when the firewall is optimized.

    If you are moving your site to a new server we recommend that you first remove extended protection. When your site has been migrated, you will then optimize the Firewall again.

    Optionally, you can choose to reset Wordfence and only migrate your settings. This will remove Firewall Optimization and all current blocks on your site.

    • Go to Dashboard > Global Options > General Wordfence Options. Enable the option “Delete Wordfence tables and data on deactivation” and save.
    • Scroll down to the section “Import/Export Options” and click “Export Wordfence Options”. Save the export token in a safe place
    • Deactivate Wordfence. Migrate your site. Activate Wordfence on the new server.
      Go to Dashboard > Global Options > Import/Export Options. Enter the export token you previously saved and click to “Import Wordfence Options”
    • Optimize the Firewall.

    This should work successfully each time when migrating.

    Let me know if this helps!

    Thanks!

    Thread Starter jstallard

    (@jstallard)

    Hi Adam

    Well, I can do all that, but it’s time-consuming. I’m migrating about 50 sites to a WordPress multisite.

    My shell scripts allow me to migrate most sites within 10 minutes. (The scripts deactivate Wordfence before migration.)

    It would be really helpful to have:
    – A wp-cli command to fix the wfHoover table problem
    – A wp-cli command to remove extended protection (especially important for non-multisite migrations)
    – or the linux command line equivalents

    Thanks
    Jackie

    Plugin Support WFAdam

    (@wfadam)

    Thanks for the suggestion for a future feature! I will pass this along to our development team!

    Thank you again for your support!

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Wordfence problems during site transfers’ is closed to new replies.