Title: Debug Log Router
Author: emberfox
Published: <strong>2026年10月18日</strong>
Last modified: 2026年10月18日

---

プラグインを検索

![](https://ps.w.org/debug-log-router/assets/banner-772x250.png?rev=3752903)

![](https://ps.w.org/debug-log-router/assets/icon-256x256.png?rev=3752903)

# Debug Log Router

 作者: [emberfox](https://profiles.wordpress.org/emberfox/)

[ダウンロード](https://downloads.wordpress.org/plugin/debug-log-router.1.0.0.zip)

 * [詳細](https://ja.wordpress.org/plugins/debug-log-router/#description)
 * [レビュー](https://ja.wordpress.org/plugins/debug-log-router/#reviews)
 *  [インストール](https://ja.wordpress.org/plugins/debug-log-router/#installation)
 * [開発](https://ja.wordpress.org/plugins/debug-log-router/#developers)

 [サポート](https://wordpress.org/support/plugin/debug-log-router/)

## 説明

Most debug log tools show you the one `debug.log` WordPress writes. Debug Log Router
splits it by the kind of request instead: an error a visitor hit on the front end,
a warning from the admin, and a failure in a background cron task land in different
files. You see at once what the error cost, and cron errors, which never show up
on any page, stop drowning in the rest.

#### Seven contexts, seven files

 * `front.log` — the public site
 * `admin.log` — the admin area
 * `ajax.log` — admin-ajax requests
 * `rest.log` — the REST API, a custom REST prefix included
 * `cron.log` — WP-Cron
 * `cli.log` — WP-CLI
 * `xmlrpc.log` — XML-RPC

Files are created as they are needed: on a site without WP-CLI, `cli.log` never 
appears. Entries are written in the usual PHP log format, so the files still open
in any text editor and over FTP.

#### Reading and downloading

 * Tools  Debug Logs, Logs tab: newest entries first, 50 at a time, up to 500 in
   the browser.
 * The plugin’s own journal is there too: what it changed in `wp-config.php` and
   in the log directory, and what it could not do.
 * Any log and the journal can be downloaded as a file from the Logs tab. The whole
   log directory downloads as a zip archive from the Settings tab if the server 
   has the PHP `zip` extension; without it, the files download one by one.
 * The old `wp-content/debug.log` is left alone and opens in the same viewer.
 * Logging is switched on and off with a single toggle on the Settings tab.
 * Errors are hidden from visitors by default. You can show them or leave it to 
   the server.

#### How the plugin handles wp-config.php

WordPress reads its debug constants before any plugin loads, so there is no way 
around `wp-config.php`. The plugin changes it once:

 * Activation changes nothing. The edit happens only when you press the button on
   the Status tab, and before you do, the tab shows exactly what will be added.
 * The edited file is checked before it replaces the original: if the result does
   not parse, or anything else in it is not as expected, `wp-config.php` stays exactly
   as it was. Its permissions, owner and group are kept.
 * A short block is added that loads the plugin’s loader and names the plugin’s 
   folder in uploads. All settings live there and in the database: switching logging
   and changing other settings never touch `wp-config.php` again.
 * Existing `define()` lines for `WP_DEBUG`, `WP_DEBUG_LOG` and `WP_DEBUG_DISPLAY`
   are not deleted but commented out, marked `DLOGR-DISABLED`.
 * If the file cannot be written, the plugin shows the ready-made snippet, the line
   number where it goes and a copy button.
 * The block is removed with the “Remove the setting from wp-config.php” button 
   or when the plugin is deleted, and the commented-out lines are restored.
 * If the plugin files are deleted over FTP, the block does nothing and the site
   keeps working.
 * The Status tab warns you when the same constants are defined above the block,
   and when the block is in place but the plugin is not loaded, for example after
   the site has moved, and offers a button that writes the block again with the 
   current paths.

#### Log directory

Logs are kept in `wp-content/uploads/debug-log-router/dlogr-logs-xxxxxxxx` (wherever
your uploads folder is), where the last eight characters are random. The name is
the main protection: the directory’s address cannot be guessed. The second layer
is an `.htaccess` file that blocks direct access on Apache and LiteSpeed. If the
name ever leaks, one button gives the directory a new one. No PHP files are written
to the uploads folder.

#### Privacy

The plugin sends no data off your server and contacts no external services. Keep
in mind that PHP logs themselves can contain paths on disk, pieces of SQL queries
and data of your site’s users. That is why only administrators can see them and 
why the log directory is protected as described above. The plugin’s journal records
which user performed each action.

#### Multisite

WordPress networks (multisite) are not supported: the plugin has not been tested
on them and makes no claim to work there.

#### Languages

The plugin’s texts follow the language of your WordPress profile; translations arrive
as language packs from translate.wordpress.org. On the Settings tab the plugin’s
page can be switched to English on its own, while the rest of WordPress keeps your
language: handy when you look up an error message or send a screenshot to support.

#### Support

The Support tab explains what the plugin does and where to report bugs, and shows
the version and licenses.

#### Credits

Icons by Lucide (https://lucide.dev), ISC license. Some icons come from the Feather
project, MIT license. The license texts are in `assets/icons/LICENSE`.

## スクリーンショット

[⌊Logs tab: front.log, newest entries first, each entry's type as a colored label;
a long stack trace scrolls inside its row. Above: the seven files by request type
and the plugin's journal.⌉⌊Logs tab: front.log, newest entries first, each entry's
type as a colored label; a long stack trace scrolls inside its row. Above: the seven
files by request type and the plugin's journal.⌉[

Logs tab: `front.log`, newest entries first, each entry’s type as a colored label;
a long stack trace scrolls inside its row. Above: the seven files by request type
and the plugin’s journal.

[⌊The plugin's own journal: changes to wp-config.php, logging switched on, log directories
created, renamed and repaired, errors, and who did it.⌉⌊The plugin's own journal:
changes to wp-config.php, logging switched on, log directories created, renamed 
and repaired, errors, and who did it.⌉[

The plugin’s own journal: changes to `wp-config.php`, logging switched on, log directories
created, renamed and repaired, errors, and who did it.

[⌊Status tab before setup: exactly what will be added to wp-config.php and where,
and which lines will be commented out. Nothing changes until you press the button.⌉⌊
Status tab before setup: exactly what will be added to wp-config.php and where, 
and which lines will be commented out. Nothing changes until you press the button
.⌉[

Status tab before setup: exactly what will be added to `wp-config.php` and where,
and which lines will be commented out. Nothing changes until you press the button.

[⌊Settings tab before setup: the log directory (rename, download as an archive) 
and what to delete along with the plugin.⌉⌊Settings tab before setup: the log directory(
rename, download as an archive) and what to delete along with the plugin.⌉[

Settings tab before setup: the log directory (rename, download as an archive) and
what to delete along with the plugin.

## インストール

 1. Install and activate the plugin. Activation changes neither `wp-config.php` nor
    any files on disk.
 2. Go to Tools  Debug Logs, Status tab.
 3. Press “Set up and enable logging”. The plugin adds its block to `wp-config.php`
    and creates the log directory.
 4. If `wp-config.php` is not writable, paste the snippet shown by hand, at the place
    indicated.

## FAQ

### Which entries never reach the plugin’s logs?

Anything that happens in `wp-config.php` above the plugin’s block: the database 
constants and salts, lines added by your host, and code loaded through `auto_prepend_file`.
Nothing inside `wp-config.php` can catch what happened before it started running.
Errors below the block, the rest of `wp-config.php` included, do reach the logs,
while the standard `debug.log` never sees them at all.

### What happened to the old debug.log?

While the plugin’s logging is on, that file is not used: entries go to the plugin’s
files instead. The old file stays where it is and opens on the Logs tab. Keep in
mind that it has no protection of its own and may be readable straight from a browser.

### I switched logging off. Did wp-config.php change?

No. The toggle only changes the plugin’s own file.

### What happens on deactivation?

Logging stops. The block stays in `wp-config.php` but does nothing until the plugin
is activated again.

### What is deleted along with the plugin?

When the plugin is deleted, it removes its block from `wp-config.php`. Everything
else goes only if you ticked it beforehand on the Settings tab. There are separate
checkboxes for the current log directory, for each directory left over from earlier
installs, and for the plugin’s data (journal and settings). Nothing is ticked by
default: you can delete the plugin and keep the logs, and the next install picks
them up. Once no log directory is left, the plugin’s folder in uploads goes too.

If the block could not be removed — for example because `wp-config.php` is not writable—
nothing is deleted. In that case, delete the lines from `BEGIN Debug Log Router`
to `END Debug Log Router` by hand and drop the `DLOGR-DISABLED` prefixes. It is 
safer to remove the block with the button on the Status tab before deleting the 
plugin: there you can see whether it worked.

### Why do entries go to the server’s log instead of the plugin’s files?

This happens when the host has fixed the PHP log path in the server configuration(
for example with `php_admin_value[error_log]`). Neither the plugin nor WordPress
itself can change it. The plugin warns about this on the Status tab and, if the 
server’s file is readable, shows it on the Logs tab. Keep in mind that such a file
may be shared by several sites on the server.

### Does the plugin keep a copy of wp-config.php?

No. Every change is checked before the file is replaced, and a change that does 
not pass leaves `wp-config.php` untouched. The plugin’s own changes are undone by
removing its block, not by restoring an old copy, so lines that other plugins or
your host added later stay in place. If you want a copy anyway, take one before 
you press the button.

### My server runs nginx. Are the logs protected?

nginx does not read `.htaccess`, so there the random directory name is the only 
protection. To close the directory completely, add a rule to your nginx configuration.

### Site Health warns that the log may be public

WordPress shows this warning for any log inside the site’s directory, judging by
the path alone. The plugin adds an explanation to the text of that check: the directory
was created by the plugin, its name is random, and it has an `.htaccess` file. The
plugin does not change the status of the check.

## 評価

このプラグインにはレビューがありません。

## 貢献者と開発者

Debug Log Router はオープンソースソフトウェアです。以下の人々がこのプラグインに貢献
しています。

貢献者

 *   [ emberfox ](https://profiles.wordpress.org/emberfox/)

“Debug Log Router” は1ロケールに翻訳されています。 [翻訳者](https://translate.wordpress.org/projects/wp-plugins/debug-log-router/contributors)
のみなさん、翻訳へのご協力ありがとうございます。

[“Debug Log Router” をあなたの言語に翻訳しましょう。](https://translate.wordpress.org/projects/wp-plugins/debug-log-router)

### 開発に興味がありますか ?

[コードを閲覧](https://plugins.trac.wordpress.org/browser/debug-log-router/)する
か、[SVN リポジトリ](https://plugins.svn.wordpress.org/debug-log-router/)をチェック
するか、[開発ログ](https://plugins.trac.wordpress.org/log/debug-log-router/)を [RSS](https://plugins.trac.wordpress.org/log/debug-log-router/?limit=100&mode=stop_on_copy&format=rss)
で購読してみてください。

## 変更履歴

#### 1.0.0

 * First release.

## メタ

 *  バージョン **1.0.0**
 *  最終更新日 **4日前**
 *  有効インストール数 **10未満**
 *  WordPress バージョン ** 5.8またはそれ以降 **
 *  検証済み最新バージョン: **7.1.3**
 *  PHP バージョン ** 7.4またはそれ以降 **
 *  言語
 * [English (US)](https://wordpress.org/plugins/debug-log-router/)、[Russian](https://ru.wordpress.org/plugins/debug-log-router/).
 *  [プラグインを翻訳](https://translate.wordpress.org/projects/wp-plugins/debug-log-router)
 * タグ
 * [debug](https://ja.wordpress.org/plugins/tags/debug/)[Debug log](https://ja.wordpress.org/plugins/tags/debug-log/)
   [error log](https://ja.wordpress.org/plugins/tags/error-log/)[log viewer](https://ja.wordpress.org/plugins/tags/log-viewer/)
   [wp-config](https://ja.wordpress.org/plugins/tags/wp-config/)
 *  [詳細を表示](https://ja.wordpress.org/plugins/debug-log-router/advanced/)

## 評価

レビューはまだ送信されていません。

[Your review](https://wordpress.org/support/plugin/debug-log-router/reviews/#new-post)

[すべてのレビューを見る](https://wordpress.org/support/plugin/debug-log-router/reviews/)

## 貢献者

 *   [ emberfox ](https://profiles.wordpress.org/emberfox/)

## サポート

意見や質問がありますか ?

 [サポートフォーラムを表示](https://wordpress.org/support/plugin/debug-log-router/)

## 寄付

このプラグインが今後も改善できるよう応援しませんか ?

 [ このプラグインに寄付 ](https://ko-fi.com/ember_fox)