Error Log Monitor


Этот плагин добавляет блок в Консоль, который отображает последние сообщения из вашего журнала ошибок PHP. Он также может отправлять вам уведомления по электронной почте о новых зарегистрированных ошибках.


  • Автоматически определяет местоположение журнала ошибок.
  • Подсказывает, как настроить регистрацию ошибок PHP, если это еще не включено.
  • Настройка отображения количества записей журнала.
  • Отправляет вам уведомления по электронной почте о зарегистрированных ошибках (дополнительно).
  • Настройка адреса электронной почты и частота получения уведомлений.
  • Вы можете легко очистить файл журнала.
  • Блок в консоли виден только администраторам.
  • Оптимизирован для работы даже с очень большим файлом журнала.


После установки плагина перейдите в раздел Консоль — Главная и включите блок «Журнал ошибок PHP» на панели «Настройки экрана». Блок должен автоматически отображать последние 20 строк из вашего журнала ошибок PHP. Если вместо этого появляется сообщение об ошибке, например «Регистрация ошибок отключена», следуйте отображаемым инструкциям для настройки регистрации ошибок.

Уведомления по электронной почте по умолчанию отключены. Чтобы включить их, нажмите ссылку «Настроить» в правом верхнем углу блока и введите свой адрес электронной почты в поле «Периодическая отправка сообщений об ошибках на электронную почту:». При желании вы также можете изменить частоту получения писем, выбрав минимальный интервал времени из раскрывающегося списка «Как часто отправлять электронную почту».


  • Блок "Журнал ошибок PHP" добавленный плагином.
  • Экран настройки блока в Консоли.


Выполните следующие действия, чтобы установить плагин на свой сайт:

  1. Загрузите файл .zip на свой компьютер.
  2. Перейдите в раздел Плагины -> Добавить новый и нажмите на кнопку «Загрузить плагин».
  3. Загрузите файл .zip.
  4. Активируйте плагин на странице Плагины -> Установленные.
  5. Перейдите в раздел Консоль — Главная и включите блок «Журнал ошибок PHP» через панель «Настройки экрана».
  6. (Необязательно) Нажмите на ссылку «Настроить» в правом верхнем углу блока, чтобы настроить плагин.


I have now been using the pro version of this plugin for 3 years. It has become an essential tool in my plugin development, in a real environment vs a staging area. Over and over again, I have also been able to track down problems in other plugins, notifying the designer or disabling accordingly. Highly recommended.
This plugin requires an opt-in for permissions before it does anything. It's supposed to display PHP logs locally. Yet it requires an opt-in for permissions to reach out and send stuff through another service. 👎
Hello, It's a decent plugin who unfortunately lost 2 stars because it's leaving a mess when deleted. - It keeps the folder with it's own log file and data. - The cron job remains. - All the tables are left in the database. I will be glad to review this rating when you offer a clean uninstall of Error Log Monitor plugin. The bare minimum would be to have a website page listing everything that needs to be manually deleted upon uninstall. Quite basic. Thank you.
This plugin does the job of showing the error messages very well! It is easy to use. I'm very happy with the plugin just it could have been better if they can add functionality for showing it in a separate tab instead of the dashboard.
The plugin is not at all what it promises to be, does not give you a dashboard settings/monitoring option, and has to be deactivated manually from the backend since it breaks the website!
Посмотреть все 39 отзывов

Участники и разработчики

«Error Log Monitor» — проект с открытым исходным кодом. В развитие плагина внесли свой вклад следующие участники:


«Error Log Monitor» переведён на 6 языков. Благодарим переводчиков за их работу.

Перевести «Error Log Monitor» на ваш язык.

Заинтересованы в разработке?

Посмотрите код, проверьте SVN репозиторий, или подпишитесь на журнал разработки по RSS.

Журнал изменений


  • Fixed a number of PHP 8 deprecation warnings and compatibility issues.
  • Tested with WP 6.1.


  • Added an «Ignored regular expressions» setting. Enter one or more regex patterns in the box and the plugin will hide log entries that match any of those patterns.


  • Added a «Clear Fixed Messages» button.
  • Fixed a scheduling bug where, in certain configurations, the plugin would send some email notifications too late.
  • Fixed a security issue.
  • Tested with WP 5.9.1 and 6.0-alpha (briefly).


  • Added a «mark as fixed» option. Like the «ignore» option, «mark as fixed» hides all existing copies of a specific error. However, if the same error happens again in the future, the plugin will make it visible again.
  • Added a «Clear Ignored Messages» button. It un-ignores all previously ignored messages.
  • Fixed a couple of PHP 8 deprecation warnings about a required parameter following an optional parameter.
  • Tested with WP 5.6.1 and 5.7-beta.


  • Fixed «Deprecated: contextual_help is deprecated since version 3.3.0». While this plugin doesn’t use the «contextual_help» filter, it includes a copy of scbFramework that can also be used by other active plugins. Some of those plugins could run code in scbFramework that used «contextual_help». This deprecated code has now been removed.
  • Tested with WP 5.5.3.


  • Fixed recoverable fatal errors being incorrectly presented as an unknown error type.
  • Added text domain to a UI message that was missing it.
  • Updated the Freemius SDK to version 2.4.1.
  • Tested with WP 5.5.1 and 5.6-beta.


  • Changed the minimum required PHP version to 5.6.
  • Tested up to WP 5.5.


  • Fixed a bug where the plugin could freeze or crash while trying to parse extremely long log entries (e.g. more than a million characters long).
  • Updated the Freemius SDK to version 2.3.2.
  • Tested up to WP 5.4.1.


  • Fixed the erorr «call to undefined function get_blog_list()» when trying to access the network admin on a non-Multisite site.


  • Fixed a conflict with WP-PageNavi, again. The fix included in the previous version was not fully effective.


  • Fixed a conflict with WP-PageNavi that could cause a fatal error.
  • Updated Freemius SDK to the latest version, which may fix some Freemius-related issues.
  • Tested up to WP 5.3.


  • Improved the way the plugin displays truncated stack traces. Now it should no longer display the last entry as a very tall and narrow block of text.
  • Added a workaround for conflicts with plugins that use old versions of scbFramework.
  • Tested up to WP 5.2.


  • Fixed a bug where it wasn’t possible to filter out log entries that didn’t match any of the standard severity levels (notice, warning, error, etc). Now you can hide uncategorized log entries by unchecking the «Other» option in filter settings.
  • Fixed a security issue.
  • Tested with the final WP 5.1 release.


  • Changed plugin configuration permissions. Now you need to have the «install_plugins» capability to change the configuration. Previous versions used the «update_core» capability.
  • Fixed a bug where users who couldn’t change plugin configuration were still shown a useless «Submit» button.
  • Tested with WP 5.1-alpha.


  • Added a workaround for a conflict with «Go Fetch Jobs (for WP Job Manager)» 1.4.6.
  • Tested with the final WP 5.0 release.


  • Added a setup wizard that helps new users create a log file and enable error logging. You can still do it manually you prefer. The setup notice will automatically disappear if logging is already configured.
  • Fixed a bug where activating the plugin on individual sites in a Multisite network could, in some cases, trigger a fatal error.
  • Additional testing with WP 5.0-alpha.


  • Fixed the «upgrade» link being broken in certain configurations.


  • Added a colored dot showing the severity level to each error message. Fatal errors are red, warnings are orange, notices and strict-standards messages are grey, and custom or unrecognized messages are blue.
  • Added a new setting for email notifications: «how often to check the log for new messages».
  • Added a notice explaining how to configure WordPress to log all types of errors (including PHP notices) instead of just fatal errors and warnings.
  • Added Freemius integration.
  • Added a link to the Pro version to bottom of the widget.
  • Improved parsing of multi-line log entries. Now the plugin will show all of the lines as part of the same message instead of treating every line as an entirely separate error.
  • Improved stack trace formatting.
  • In Multisite, the dashboard widget now also shows up in the network admin dashboard.
  • Changed permissions so that only Super Admins can change plugin settings or clear the log file. Regular administrators can still see the widget.


  • The widget now displays log timestamps in local time instead of UTC.
  • Fixed a runtime exception «Backtrack buffer overflow» that was thrown when trying to parse very long log entries.


  • The dashboard widget now shows the log file size and the «Clear Log» button even when all entries are filtered out.
  • Tested with WP 4.9 and WP 5.0-alpha.


  • Fixed two PHP notices: «Undefined index: schedule in […]Cron.php on line 69» and «Undefined index: time in […]Cron.php on line 76».
  • Added «error_reporting(E_ALL)» to the example code to log all errors and notices.
  • Tested up to WP 4.9-beta2.


  • Fixed the error «can’t use method return value in write context». It was a compatibility issue that only affected PHP versions below 5.5.


  • You can send email notifications to multiple addresses. Just enter a comma-separated list of emails.
  • Made sure that email notifications are sent no more often than the configured frequency even when WordPress is unreliable and triggers cron events too frequently.
  • Tested up to WP 4.9-alpha-40871.


  • Fixed a fatal error caused by a missing directory. Apparently, SVN externals don’t work properly in the plugin repository.


  • Added an option to ignore specific error messages. Ignored messages don’t show up in the dashboard widget and don’t generate email notifications, but they stay in the log file.
  • Added limited support for parsing stack traces generated by PHP 7.
  • Made the log output more compact.
  • Improved log parsing performance.
  • Fixed an «invalid argument supplied for foreach» warning in scbCron.


  • Added a severity filter. For example, you could use this feature to make the plugin send notifications about fatal errors but not warnings or notices.
  • Added limited support for XDebug stack traces. The stack trace will show up as part of the error message instead of as a bunch of separate entries. Also, stack trace items no longer count towards the line limit.


  • Hotfix for a parse error that was introduced in version 1.4.1.


  • Fixed a PHP compatibility issue that caused a parse error in Plugin.php on sites using an old version of PHP.


  • Added an option to send an email notification when the log file size exceeds the specified threshold.
  • Fixed a minor translation bug.
  • The widget now shows the full path of the WP root directory along with setup instructions. This should make it easier to figure out the absolute path of the log file.
  • Tested with WP 4.6-beta3.


  • Added i18n support.
  • Added an elm_show_dashboard_widget filter that lets other plugins show or hide the error log widget.
  • Tested with WP 4.5.1 and WP 4.6-alpha.


  • Tested up to WP 4.5 (release candidate).


  • Added support for Windows and Mac style line endings.


  • Added an option to display log entries in reverse order (newest to oldest).
  • Added a different error message for the case when the log file exists but is not accessible.
  • Only load the plugin in the admin panel and when running cron jobs.
  • Fixed the error log sometimes extending outside the widget.
  • Tested up to WP 4.4 (alpha version).


  • Tested up to WP 4.2 (final release).
  • Added file-based exclusive locking to prevent the plugin occasionally sending duplicate email notifications.


  • Tested up to WP 4.2-alpha.
  • Refreshing the page after clearing the log will no longer make the plugin to clear the log again.


  • Updated Scb Framework to the latest revision.
  • Tested up to WordPress 4.0 beta.