Debugging is enabled. However, the debug.log file does not exist

It could be a couple of things.

1. There are no errors. If the debug.log file is not present, it will be created when there is an error. Conversely, if it doesn’t exist and there are no errors it won’t be created until there is an error.

2. If you have errors but debug.log is not being created, one reason could be apache doesn’t have write permissions on wp-content (the directory WP_CONTENT_DIR is set to) directory.

I have the same issue. It does not create the debug.log file. But however it does work on another website using the same server and settings. The directories on both are set to the same, readable and write-able.

I did manually add the debug file to the non working domain and it will read it, but never will write to it. Any ideas?

Debugging is enabled. However, the debug.log file does not exist or was not found.

Ideeas ? same problem.

I would do the following:

1. Confirm that both WP_DEBUG and WP_DEBUG_LOG are true.
2. Make sure apache can write to wp-content or whatever directory the const WP_CONTENT_DIR is set to.

Having the same issue.

1. wp-content directory is writable (755), wordpress writes content all the time.

2. in wp-config

define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);
@ini_set('display_errors',0);
@ini_set("error_log", dirname(__FILE__).'/wp-content/debug.log');

3. manually trying to write custom logs
error_log('#test: Test.');

4. Error:
Debugging is enabled. However, the debug.log file does not exist or was not found.

Any Ideas?

update #1: if i manually create the debug.log file the plugin finds it and shows 0 errors. but still no luck writing to it.

update #2: think i found the issue. if i run phpinfo the error_log location is being overridden by the server and @ini_set isn’t overwriting it. neither is php.ini or .user.ini. looks like this is hard set in the server config and not user changeable.

SOLUTION: since I couldn’t change the error_log location, i created a symlink from the location and filename the plugin is expecting to the actual location and file. The logging now appears to be working as expected. Hope this helps someone in the future with the same issue. cheers.

Any Ideas?

• This reply was modified 8 years, 1 month ago by redesigned.
• This reply was modified 8 years, 1 month ago by redesigned.
• This reply was modified 8 years, 1 month ago by redesigned. Reason: solution