The Logs page says No logs found, but you think there are errors. Check these things, one by one.
1. Maybe there are no errors #
An empty log is good news. If your site works and you see no errors, there may be nothing to fix.
2. Check that logging is on #
- Go to
BugTrace → Settings. - Make sure
WP_DEBUGandWP_DEBUG_LOGare both on. - Click Save Settings.
- Open the page that has the problem again. Then refresh the Logs page.
If you cannot save, read Fix “wp-config.php is not writable”.
3. Reset your search and filter #
BugTrace remembers your last search and filter. On the Logs page:
- Empty the Search… box.
- Set the type filter to All.
4. Check where your log is saved #
BugTrace reads the log from one of these places:
| In wp-config.php | Log file |
|---|---|
define( 'WP_DEBUG_LOG', true ); | wp-content/debug.log |
define( 'WP_DEBUG_LOG', '/path/to/file.log' ); | The file you set |
Some hosts save PHP errors to another file with a PHP setting (error_log). BugTrace cannot read that file. Ask your host where PHP errors are saved.
5. Check the date format in the log #
BugTrace reads lines that start with a date like this:
[25-Sep-2026 09:40:36 UTC]
If your server writes dates in another format, BugTrace may not show the errors. Download the log to check it.
6. “Constant WP_DEBUG_LOG already defined” #
You may see a warning like this:
Constant WP_DEBUG_LOG already defined
This means WP_DEBUG_LOG is set in two places. For example, your host sets it, and BugTrace adds it to wp-config.php too. Open wp-config.php and remove one of the two lines. Or ask your host.