Broken site

  • Resolved Aeniss

    (@aeniss)


    2 years, 7 months ago

    Hi,

    We have had an installation of your plugin for about one year or more now, and did not experience any issues so far. Now, all of a sudden, our backend website broke. We were not able to use several functions on our website. After deactivating all plugins, then reactivate them one by one, while debugging, we’ve found out it was your plugin the one causing all the mess.

    Here are the messages that our debugging log is showing when your plugin is active (I have removed the first two locations in the strings above, for security):

    ****************

    Notice: Constant DISALLOW_FILE_EDIT already defined in public_html/wp-config.php on line 80

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

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

    Warning: Cannot modify header information – headers already sent by (output started at public_html/wp-config.php:80) in public_html/wp-includes/pluggable.php on line 1435

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

    **********

    If I deactivate your plugin, the debug is not showing any warnings. When I activate it again, the warnings show up and the site does not work properly.

    We will appreciate you help with sorting out and fixing this issue.

    Best regards,

    Tony

    The page I need help with: [log in to see the link]

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support Jarno Vos

    (@jarnovos)

    2 years, 7 months ago

    Hi @aeniss,

    It looks like you’ve activated the “Disable the built-in file editors” feature under Settings > Hardening in Really Simple SSL, while you already have a rule added to your wp-config.php which does that.

    The solution to the warning should therefore be to either remove that line from your wp-config.php, or disable this feature in Really Simple SSL.

    Kind regards, Jarno

    Thread Starter Aeniss

    (@aeniss)

    2 years, 6 months ago

    Hi,

    Thank you for your prompt response. I disabled that function in your plugin and everything works fine now. It was always enabled before and we never had any issues so far. I guess it started to conflict with another plugin or the theme itself after some new update.

    Have a wonderful weekend!

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

The topic ‘Broken site’ is closed to new replies.