WordPress php errors plugin

WordPress php errors plugin

Installation

Follow these steps to install the plugin on your site:

1. Download the .zip file to your computer.
2. Go to Plugins -> Add New and select the “Upload” option.
3. Upload the .zip file.
4. Activate the plugin through the *Plugins -> Installed Plugins” page.
5. Go to the Dashboard and enable the “PHP Error Log” widget through the “Screen Options” panel.
6. (Optional) Click the “Configure” link in the top-right of the widget to configure the plugin.

Reviews

Crashed site

In spite of repeated support threads about it, this plugin doesn’t limit to the log file size. Twice it’s used all available storage and caused a site to crash. Today, a 100GB log file.This shouldn’t be a fancy feature, it’s basic best practice to code plugins in ways that don’t crash sites.The widget itself is otherwise handy and convenient.

Gatekeeps disabling their plugin

Any plugin that blocks its own deactivation to force a feedback prompt gets an instant bad review in my book.You want feedback? Do better!

A Great Program with Good Support

Excellent Plugin

Quite Good but No Display full Log Option (or other filtering)

It is certainly useful and has a few options but installation is manual. It doesn’t have any display log option to view filtered out messages. Email notification doesn’t seem to work. I’m not sure about those people complaining about no clean uninstall, I don’t see how they could expect that given that there was no installation done by the plugin (therefore no «clean install» either).

Excellent and helpful

A very helpful tool for efficient debugging. The pro version provides stack trace and context. Thank you!

Contributors & Developers

“Error Log Monitor” is open source software. The following people have contributed to this plugin.

“Error Log Monitor” has been translated into 7 locales. Thank you to the translators for their contributions.

Interested in development?

Changelog

1.7.7

1.7.6

1.7.5

• Fixed a visual bug where the log size limit field was too narrow in the most recent WP version.
• Tested with WP 6.2.

1.7.4

• Updated the Freemius SDK to version 2.5.3 in the hopes of fixing a couple of PHP 8.1 deprecation notices that appear to be triggered by the SDK.

1.7.3

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

1.7.2

• 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.

1.7.1

• 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).

1.7

• 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.

1.6.13

• 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.

1.6.12

• 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.

1.6.11

1.6.10

• 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.

1.6.9

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

1.6.8

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

1.6.7

• 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.

1.6.6

• 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.

1.6.5

• 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.

1.6.4

• 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.

1.6.3

• 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.

1.6.2

• 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.

1.6.1

1.6

• 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.

1.5.7

• 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.

1.5.6

• 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.

1.5.5

• 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.

1.5.4

• 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.

1.5.3

• 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.

1.5.2

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

1.5.1

• 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.

1.5

• 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.

1.4.2

1.4.1

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

1.4

• 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.

1.3.3

• 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.

1.3.2

1.3.1

1.3

• 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).

1.2.4

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

1.2.3

• 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.

1.2.2

Meta

• Version: 1.7.7
• Last updated: 2 weeks ago
• Active installations: 20,000+
• WordPress Version: 4.5 or higher
• Tested up to: 6.2.2
• PHP Version: 5.6 or higher
• Languages:

Источник

WordPress php errors plugin

Installation

Bugsnag is available through the WordPress Plugins Directory, so you can download and install automatically from the Plugins menu on your WordPress admin page.

To manually install Bugsnag:

1. Unzip bugsnag-wordpress.zip
2. Upload the bugsnag directory from the zip file to the /wp-content/plugins/ directory
3. Activate the plugin through the ‘Plugins’ menu in WordPress
4. Click the ‘configure’ link next to the Bugsnag plugin, and follow the instructions

Reviews

Excellent error monitoring

Been using it now for several years and it helped me often quickly finding (hidden) issues across a multitude of pages and functionality.

Abandoned.

This plugin used to be one of the best tools out there, however, it seems like is not being maintained anymore. There is no support for the recent releases of PHP (8.0, 8.1). Recent support requests are not being handled anymore as well.

Works great, people are just dumb

Easy error monitoring

The plugin is easy to set up; all errors can be monitored via the Bugsnag dashboard. You can also set different log levels and differ between the environments (dev/production) of your website. Bonus: There are lots of cool integrations like Slack (Push Notifications), GitHub (New Issues) and much more!

Does exactly what it is supposed to in my experience

I have installed the plugin on about 40 sites today so far, and it installed successfully on all of them and has logged errors on many of them already. The integration has been seamless. The one aspect which has not been quite seamless is that, after installing the plugin, trying to enable it from the confirmation screen often gives me a 500 error in Pantheon (our hosting provider). I then have to go to the main Plugins page and enable it there, where it works 100% of the time.

Contributors & Developers

“WordPress Error Monitoring by Bugsnag” is open source software. The following people have contributed to this plugin.

Источник