Fatal Error Notify 1.4.4

Does Fatal Error Notify work with WordPress 5.9 and PHP 7.4.8? A smoke test was performed on .

Summary

Errors
1PHP notices
No JavaScript exceptions
All test pages loaded successfully
No resource errors
Performance

Memory usage: 5.4 KiB
The average PHP memory usage increased by this amount after activating by the plugin.

Page speed impact: insignificant.
The plugin didn't make the site noticeably slower.

Environment
WordPress version5.9
PHP version7.4.8
MySQL version8.0.21
PHP memory limit256M
Plugin Info
Last updated
Active installs 7,000+
WordPress.org page https://wordpress.org/plugins/fatal-error-notify/
Badges

WordPress compatibility badge PHP compatibility badge

Get badge code

Pages 3

Plugins ‹ Test site — WordPress

Page screenshot: Plugins ‹ Test site — WordPress
URL /wp-admin/plugins.php?plugin_status=all&paged=1&s
Requested URL /wp-admin/plugins.php?action=activate&plugin=fatal-error-notify%2Ffatal-error-notify.php&plugin_status=all&paged=1&s&_wpnonce=bb7c2265da
Aspect after-activation
HTTP status 200
Load time 0.358 s
Memory usage 3.27 MiB
JS errors None
Resource errors None

Settings → Fatal Error Notify

Page screenshot: Settings → Fatal Error Notify
URL /wp-admin/options-general.php?page=fatal_error_notify
Aspect menu-item
HTTP status 200
Load time 0.245 s
Memory usage 3.23 MiB
JS errors None
Resource errors None

Test site – Just another WordPress site

Page screenshot: Test site – Just another WordPress site
URL /
Aspect front-page
HTTP status 200
Load time 0.264 s
Memory usage 3.36 MiB
JS errors None
Resource errors None

Benchmark

URL Load time Memory usage
Inactive Active Change Inactive Active Change
/wp-admin/index.php0.335 s0.245 s-0.090 s3.36 MiB3.37 MiB+ 8.76 KiB
/wp-admin/edit.php0.165 s0.173 s+0.008 s3.39 MiB3.4 MiB+ 8.76 KiB
/wp-admin/post-new.php0.784 s0.917 s+0.133 s6.15 MiB6.16 MiB+ 13.12 KiB
/wp-admin/upload.php0.339 s0.301 s-0.038 s3.24 MiB3.25 MiB+ 7.63 KiB
/wp-admin/options-writing.php0.262 s0.129 s-0.133 s3.24 MiB3.24 MiB- 536 bytes
/wp-admin/media-new.php0.275 s0.171 s-0.104 s3.22 MiB3.24 MiB+ 15.8 KiB
/wp-admin/edit-tags.php?taxonomy=category0.329 s0.165 s-0.164 s3.25 MiB3.27 MiB+ 16.7 KiB
/wp-admin/post-new.php?post_type=page0.667 s0.803 s+0.136 s6.14 MiB6.15 MiB+ 8.7 KiB
/wp-admin/options-discussion.php0.229 s0.258 s+0.029 s3.22 MiB3.23 MiB+ 16.11 KiB
/wp-admin/edit-comments.php0.196 s0.187 s-0.009 s3.26 MiB3.27 MiB+ 7.61 KiB
/0.256 s0.197 s-0.059 s3.4 MiB3.36 MiB- 43.3 KiB
Average 0.349 s0.322 s-0.026 s3.81 MiB3.81 MiB+ 5.4 KiB

Code Statistics

Note: Third-party libraries and minified JS/CSS files are excluded from these statistics where possible, so the numbers you see here may be lower than those reported by other tools.

PHP
CSS
Language % Lines of code Comment lines Files
PHP83.0%2881403
CSS13.0%4571
JavaScript4.0%1401
Total 347 147 5

PHP Code Analysis | More results »

Lines of code 308
Total complexity 61
Median class complexity 18.0
Median method complexity 1.0
Most complex class Fatal_Error_Notify
Most complex function Fatal_Error_Notify_Admin::settings_page()
Classes 3
Methods 14
Functions 1

Additions

Things that the plugin adds to the site. This section is not intended to be comprehensive. The test tool only looks for a few specific types of added content.

No new entries found.

PHP Error Log 1 lines

[27-Jan-2022 19:45:18 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5768
See also: All tests for this plugin, How to Hide the "Fatal Error Notify" Admin Menu