The wp-config.php file is not writable. Please check the file permissions.

  • Recent changes to the plugin added some options for defaulting wp_debug_enabled and wp_debug_log_enabled to true by default. It then attempts to modify the wp-config.php file based on these default values and calls wp_die() when it can’t. Many hosting providers, including WordPress.com, may not allow modifying files this way for security reasons.

    Rather than calling wp_die(), can you call error_log() or trigger_error() instead, which is more friendly and allows a site to still function? Additionally, you may want to consider setting the options to false by default rather than true as most good hosting providers display all PHP errors within their dashboards, regardless of the wp-config.php constants.

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

  • I’ve had the same problem with our sites running this plugin.

    v 1.71 worked but 1.73 and 1.74 crash the site and display the same error “The wp-config.php file is not writable”

    I reported this directly to SA yesterday and hoped the 1.74 would fix the problem but it hasn’t.

    Thread Starter mtg169

    (@mtg169)

    Yeah, this debugging change that’s enabled by default and attempts to modify the wp-config.php was introduced in 1.7.2. It seems like a bad way to try and use debugging/logging in their plugin when there are better and more efficient ways to do it. There is no need for a plugin to modify wp-config.php to debug or have its own log file.

    Here are the relevant diffs:

    I deactivated on multiple sites for the time being. WordPress.com is considering adding it to their Incompatible Plugin list if not fixed so none of their users can install it since it will break their site and make it inaccessible.

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