DISALLOW_FILE_EDIT already defined

Hi @gopa4

Wordfence doesn’t have an option to set the WordPress DISALLOW_FILE_EDIT constant.

The PHP notice means that you have the line of code replicated more than once somewhere in your WordPress file system.

Hi @wfphil

I have found it with String locator plugin. The code was 2x in my wp-config.php:)
Thanks!
Case Closed!

• This reply was modified 3 years, 9 months ago by gopa4.

Hi @gopa4

The PHP notice error means that you have the line of code below existing more than once somehere in your WordPress file system.

define( ‘DISALLOW_FILE_EDIT’, true );

I can’t tell you where that might be. You could ask your hosting provider to search for it using the command line interface on the server to see in which files the string DISALLOW_FILE_EDIT has been set.

Note that it is found in the wp-includes/capabilities.php file twice.

Hi @gopa4

With regards my reply above. If your hosting provider does help you then the DISALLOW_FILE_EDIT string will also be found in the two Wordfence files below, but this is for just for the state status reporting in the WordPress Settings section on the Tools >> Diagnostics page:

wordfence/lib/menu_tools_diagnostic.php
wordfence/views/diagnostics/text.php

Hi @wfphil

I have found it with String locator plugin (it was very easy to find). The code was 2x in my wp-config.php:)
Thank you for your information!
Case Closed!Thank you for your help.

PS: We are on a shared hosting. Can automatic scans be only performed during certain hours (at night) or disabled (paused) during rush hours?

Hi @gopa4

Glad to hear you found the duplicate line.

Users of the free version of the plugin cannot schedule scans. You can read more about scan scheduling here:

https://www.wordfence.com/help/scan/scheduling/