WordPress error log viewer without a server login

When WP_DEBUG and WP_DEBUG_LOG are both enabled in wp-config.php, WordPress writes errors to debug.log in the wp-content folder. Hosts also keep their own PHP error logs, in a location that varies by server. In CMDPress, a connected site’s logs open from its record, so the first look needs no server or FTP login.

Edit wp-config.php and set WP_DEBUG and WP_DEBUG_LOG to true, plus WP_DEBUG_DISPLAY to false so errors stay off the page, above the line that says to stop editing. WordPress then writes to wp-content/debug.log. Turn debugging off when you finish, because that file can be reachable from the web.

Usually because WP_DEBUG is not true, the constants were added at the bottom of wp-config.php after WordPress loads, or the web server cannot write to wp-content. The file also stays absent until an error, warning or notice actually occurs. If WP_DEBUG_LOG is set to a file path instead of true, the log is written there.

Open the site in CMDPress and choose logs. Match error details and timestamps to when the problem started, then compare the site’s recent activity and latest backup, which sit one step away. That makes the next move, whether a fix or a restore, an informed choice rather than a guess.