• Resolved homepagestore

    (@homepagestore)


    I developed a website in a folder named /wp/. After moving the website into production by moving it to the root folder, I kept getting an error even after changing all references in the database from /wp/ to /. I eventually found that the file user.ini has a reference to the file wordfence-waf.php in the old /wp/ folder. Before finding that reference, I tried deactivating Wordfence and deleting it and still the user.ini file remained. I am letting you know about this because traditional methods to move a website in production do not work with the way you are referencing the folder. I think when the delete option is taken the user.ini file should be deleted.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Hi,
    In general, it’s recommended to disable the firewall before migrating WordPress installation with Wordfence plugin installed, then re-configure the firewall again once your site is moved, please check “Migrating Wordfence” guide on our docs.

    Thanks.

    Hi @homepagestore
    Since I haven’t heard back from you I am assuming that the instructions helped you solve your issue so I am marking this topic as resolved.

    If however, for whatever reason, you are still experiencing this issue and it is not resolved please respond to the post, which will move it back up the queue, and mark this topic as “not resolved”.

    Thank you.

    Thread Starter homepagestore

    (@homepagestore)

    Good day wfakaa,
    I think you missed my suggested that the user.ini be deleted when the plugin is deleted or perhaps you should provide a way to edit the URL in the settings of Wordfence. I love your extension, I use it on three client websites. Please log this as a feature request.
    Thank you,
    Richard

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘user.ini file retains reference to folder when moving into production’ is closed to new replies.