Error after Wordfence and Sucuri deleted?

  • Dears,

    Am a big fan for solid, and I staring to remove all old security plugins because my aws access key related to send mails service taken and hacked !!

    my old security are:

    Wordfence Security

    Sucuri Security

    after I deleted them I get this messages:

    DISALLOW_FILE_EDIT already defined in?/home/hormxwbz/public_html/wp-config.php?on line?53

    Warning: Cannot modify header information – headers already sent by (output started at /home/hormxwbz/public_html/wp-config.php:53) in /home/hormxwbz/public_html/wp-admin/includes/misc.php on line 1438

    Warning: Cannot modify header information – headers already sent by (output started at /home/hormxwbz/public_html/wp-config.php:53) in /home/hormxwbz/public_html/wp-includes/functions.php on line 7137

    Warning: Cannot modify header information – headers already sent by (output started at /home/hormxwbz/public_html/wp-config.php:53) in /home/hormxwbz/public_html/wp-admin/admin-header.php on line 9

    and solid setup stopped in the scan part, no scan or skip !!

    what I have to do?

    note:

    I still used Really Simple Security plugin

    • This topic was modified 3 months, 2 weeks ago by ahmedalnaqa.
Viewing 1 replies (of 1 total)
  • Plugin Support chandelierrr

    (@shanedelierrr)

    Hi @ahmedalnaqa,

    Glad you reached out, and very happy to hear you love Solid Security!

    Solid Security tries to add the DISALLOW_FILE_EDIT constant to the wp-config.php file by default through the Disable File Editor setting in WordPress Tweaks.?The DISALLOW_FILE_EDIT already defined message indicates that the constant is already there and/or there is more than one instance of that constant in the file.

    To resolve, kindly open the wp-config.php file using FTP/SFTP client tools like FileZilla or your hosting file manager and remove the?DISALLOW_FILE_EDIT?line that isn’t between the?BEGIN iThemes Security and?END iThemes Security?lines. Then, save your changes.

    As for the headers already sent by message, that could indicate the presence of an extra whitespace or character outputted before WordPress sends HTTP headers, usually occurring in wp-config.php file or other early loaded files. I’d recommend making sure there are no extra whitespace or characters in your wp-config.php file before the <?php?opening tag or after the ?>?closing tag (if it exists).

    Then make sure to clear all sorts of caches after applying the changes. I’d recommend clearing in this order: server cache -> CDN cache (if you use it) -> plugin cache -> browser cache.

    Hope this helps, and let me know if this helps you set up Solid Security properly!

Viewing 1 replies (of 1 total)
  • You must be logged in to reply to this topic.