Find the WordPress project
Lognivo recognizes WordPress projects from wp-settings.php and looks in wp-content among its common log directories. You can always open a readable text log directly if the site uses a custom location.
// WordPress / macOS
WordPress debugging, with the context intact.
A plugin warning, a failed request and a PHP error can live in different files. Put the WordPress debug log beside your server log and work through the evidence.
Find your planRead the practical guide ↗YOUR DEBUGGING WORKFLOW
01
wp-content/debug.log02
PHP / error.log03
web / error.log
lognivoOne workspace. Separate panels.Workflow illustration
// FROM SOURCE TO SIGNAL
A workflow you can return to.
Open debug.log and the PHP log
When WordPress debug logging is configured, select its debug.log file. Add the PHP error log as another panel. Search a plugin directory name or the error message to narrow the investigation.
Work locally or over SSH
Read local development logs or connect to a server where your SSH user can access the files. Lognivo does not enable WordPress debugging or modify wp-config.php for you.
// A CLOSER LOOK
Small controls. More room for the log.
Search, severity filters, reading order and pause stay with their panel. As you resize, secondary actions move into the options menu.
Before you connect.
Do I need a WordPress plugin?
No Lognivo plugin is required. The app reads existing text logs locally or over SSH. WordPress itself must be configured to write the log you want to inspect.
Why is debug.log missing?
Check your WordPress debug configuration, file permissions and configured log path. Start on a development or staging site. The guide explains the standard configuration and why the file may not exist yet.
Keep the rest of your stack in view.
Make room for the whole story.
macOS 14+ · Apple silicon & Intel
Get Lognivo for Mac