Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support chandelierrr

    (@shanedelierrr)

    Hello @jampotjaffa,

    Thanks for the detailed report, and we’re here to help!

    Those first two warnings:

    • <code class=””>Constant DISALLOW_FILE_EDIT already defined
    • <code class=””>Constant FORCE_SSL_ADMIN already defined

    mean those constants are being defined more than once in your wp-config.php. They’re normally written there by Solid Security, but in your case the same lines appear twice (often due to a previous iThemes/Solid config block being left in place).

    Because those warnings are being output on the page, PHP/WP cannot send redirect/login headers anymore, which then triggers <code class=””>Cannot modify header information – headers already sent …

    To resolve this, please follow these steps:

    1. Back up wp-config.php first (download a copy)
    2. In public_html/wp-config.php, ensure these are only defined once. So you’ll want to remove the duplicate copies
      1. <code class=””>define( ‘DISALLOW_FILE_EDIT’, true );
      2. <code class=””>define( ‘FORCE_SSL_ADMIN’, true );
    3. Save the changes.

    Also, please remove your <code class=””>ITSEC_ENCRYPTION_KEY from the forum post (it shouldn’t be shared publicly).

    The end result should look like:

    // BEGIN Solid Security - Do not modify or remove this line
    // Solid Security Config Details: 2
    define( 'DISALLOW_FILE_EDIT', true );
    define( 'FORCE_SSL_ADMIN', true );
    // END Solid Security - Do not modify or remove this line

    define( 'ITSEC_ENCRYPTION_KEY', '…keep-this…' );

    If you’re locked out and can’t reach wp-admin yet, you can temporarily disable Solid Security via FTP/File Manager by renaming: wp-content/plugins/better-wp-security/ to <code class=””>better-wp-security.disabled/ then try logging in again.

    Once the duplicate defines are fixed, you can rename the folder back to re-enable the plugin.

    I hope this helps.

    Thread Starter jampotjaffa

    (@jampotjaffa)

    @shanedelierrr Thanks very much for the helpful step by step advice. Your explanation tallies with what I’ve understood from our web host. I’m working my way through the steps you shared.

    To do that, 2 things that should be / might seem simple but aren’t:

    Can you please advise where to type the code you gave for step 1 and 2?

    How do I edit my initial post to remove the sensitive info? (which meant nothing to me, so I’m grateful to you for flagging this to me) I don’t seem to have an edit button/option anywhere from this post…

    Thanks in advance

    Thread Starter jampotjaffa

    (@jampotjaffa)

    Thanks again @shanedelierrr for the above help. With a bit of IT savvy help once I’d progressed as far as I could this is now resolved, so question 1 is redundant but I still can’t see how to edit my post to remove sensitive info…

    Disabling Solid Security through FTP worked but also removed the custom login I normally use. I’d forgotten about the wp-admin route/didn’t realise that would still work. So (after a few hours of overcoming one block after another in accessing FTP and disabling the plugin) when I got a 404 error for the custom login I admitted defeat and reached out to a local contact who has worked on our site before. He resolved the remaining issues very quickly and reinstated the custom login and Solid Security. Big relief!

    Plugin Support chandelierrr

    (@shanedelierrr)

    Hi @jampotjaffa,

    So sorry for the delayed response, and I’m glad you got the issues squared away!

    I’m adding some of our help articles here for future reference that can help you when you encounter those issues again:

    I’ll mark this thread resolved now, but feel free to reach out again if you need help.

    Thread Starter jampotjaffa

    (@jampotjaffa)

    Thanks. Any advice about editing my original post to remove the sensitive data. I’ve looked at everything I can think of to do this…

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

You must be logged in to reply to this topic.