• amcraftonline

    (@amcraftonline)


    I am getting errors about WP debug, debug_log, and debug_display since installing Error Log Monitor and I can’t figure out what’s causing the error. I’ve tried removing the Error Log Monitor plugin, but the issue persists. I’ve checked grep -rnw ‘/opt/bitnami/wordpress/’ -e ‘WP_DEBUG’ looking for instances of the phrase, but nothing giving me a clue as to the cause of the error.

Viewing 1 replies (of 1 total)
  • Plugin Author Janis Elsts

    (@whiteshadow)

    Normally, that warning would also include the name of the PHP file that tried to (re-)define the constant. Unless you can’t access the full warning message?

    The WP_DEBUG constant is usually defined in the wp-config.php file. It’s possible that Bitnami might be doing something special there; it’s been a while since I’ve looked at how Bitnami sets up its WordPress VMs.

    The Error Log Monitor plugin itself does not define WP_DEBUG and WP_DEBUG_DISPLAY, but it does display instructions on how to add them to the wp-config.php file if they’re not already set up in the recommended way (for example, WP_DEBUG_DISPLAY should usually be false on live sites). If the constants are already defined somewhere else, or if the suggested code gets added twice, that could cause warnings like the ones you mentioned.

Viewing 1 replies (of 1 total)
  • The topic ‘Warning: Constant WP_DEBUG already defined’ is closed to new replies.