Constant WFWAF_ENABLED already defined

  • Resolved nickpagz

    (@npagazani)


    6 years, 9 months ago

    Hi,

    I was debugging some other issues on my site and noticed this in my debug log:
    PHP Notice: Constant WFWAF_ENABLED already defined in … wp-config.php on line xx.

    It’s not a big deal, but just wondered why it’s showing up. That line in my wp-config is “define(‘WFWAF_ENABLED’, false);”

    Thanks,
    Nick

Viewing 3 replies - 1 through 3 (of 3 total)

  • Hi Nick,
    I wonder why you have added this line there in first place? this line is supposed to disable Firewall in case the plugin’s dashboard was inaccessible somehow, it should be added in wordfence-waf.php file if “Extended Protection” was enabled, and in wp-config.php if the “Basic Protection” was enabled.

    Are you sure you didn’t add a similar line anywhere else? in wordfence-waf.php maybe?

    Thanks.

    Thread Starter nickpagz

    (@npagazani)

    Maybe I did. I know with some hosts you need to jump through flaming hoops to get WF to work properly, like with SiteGround for example. But this site is on bluehost, and I don’t think I needed to do anything special.

    Anyways, thanks for the tips. I will check it out and report back.

    Thanks,
    Nick

    Thread Starter nickpagz

    (@npagazani)

    OK, so at first I thought maybe it was a subdomain with an installation on it that had WF installed. But after deleting all the subdomains I’m still getting the notice.

    It could’ve been bluehost support added it in there at one point to disable it when there was a crash I had in the past.

    Anyways, I’ve deleted the line from wp-config. The plugin shows the firewall is activated, so I’m assuming I’m good to go!

    Thanks.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Constant WFWAF_ENABLED already defined’ is closed to new replies.