1. Home
  2. Melapress File Monitor
  3. 1.6.2

Melapress File Monitor 1.6.2

Does Website File Changes Monitor work with WordPress 5.6 and PHP 7.4.8? A smoke test was performed on .

Summary

Errors
No PHP errors, warnings or notices
4JavaScript exceptions
All test pages loaded successfully
No resource errors
Performance

Memory usage: 98.24 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.6
PHP version7.4.8
MySQL version8.0.21
PHP memory limit256M
Plugin Info
Last updated
Active installs 5,000+
WordPress.org page https://wordpress.org/plugins/website-file-changes-monitor/
Badges

WordPress compatibility badge PHP compatibility badge

Get badge code

Pages 9

Website File Changes Monitor ‹ Test site — WordPress

Page screenshot: Website File Changes Monitor ‹ Test site — WordPress
URL /wp-admin/admin.php?page=wfcm-file-changes
Requested URL /wp-admin/plugins.php?action=activate&plugin=website-file-changes-monitor%2Fwebsite-file-changes-monitor.php&plugin_status=all&paged=1&s&_wpnonce=45ec0e6607
Aspect after-activation
HTTP status 200
Load time 0.681 s
Memory usage 2.99 MiB
JS errors 
[
    {
        "message": "TypeError: Cannot read property 'length' of undefined\n    at EventsProvider._callee$ (webpack-internal:///./assets/js/src/file-changes/components/context/EventsContext.js:152:45)\n    at tryCatch (webpack-internal:///./node_modules/regenerator-runtime/runtime.js:45:40)\n    at Generator.invoke [as _invoke] (webpack-internal:///./node_modules/regenerator-runtime/runtime.js:271:22)\n    at Generator.prototype.<computed> [as next] (webpack-internal:///./node_modules/regenerator-runtime/runtime.js:97:21)\n    at asyncGeneratorStep (webpack-internal:///./node_modules/@babel/runtime/helpers/asyncToGenerator.js:3:24)\n    at _next (webpack-internal:///./node_modules/@babel/runtime/helpers/asyncToGenerator.js:25:9)",
        "trace": null,
        "code": null
    }
]
Resource errors None

Files Monitor

Page screenshot: Files Monitor
URL /wp-admin/admin.php?page=wfcm-file-changes
Aspect menu-item
HTTP status 200
Load time 0.254 s
Memory usage 2.74 MiB
JS errors 
[
    {
        "message": "TypeError: Cannot read property 'length' of undefined\n    at EventsProvider._callee$ (webpack-internal:///./assets/js/src/file-changes/components/context/EventsContext.js:152:45)\n    at tryCatch (webpack-internal:///./node_modules/regenerator-runtime/runtime.js:45:40)\n    at Generator.invoke [as _invoke] (webpack-internal:///./node_modules/regenerator-runtime/runtime.js:271:22)\n    at Generator.prototype.<computed> [as next] (webpack-internal:///./node_modules/regenerator-runtime/runtime.js:97:21)\n    at asyncGeneratorStep (webpack-internal:///./node_modules/@babel/runtime/helpers/asyncToGenerator.js:3:24)\n    at _next (webpack-internal:///./node_modules/@babel/runtime/helpers/asyncToGenerator.js:25:9)",
        "trace": null,
        "code": null
    }
]
Resource errors None

Files Monitor → Modified Files

Page screenshot: Files Monitor → Modified Files
URL /wp-admin/admin.php?page=wfcm-file-changes&tab=modified-files
Aspect menu-item-tab
HTTP status 200
Load time 0.196 s
Memory usage 2.74 MiB
JS errors 
[
    {
        "message": "TypeError: Cannot read property 'length' of undefined\n    at EventsProvider._callee$ (webpack-internal:///./assets/js/src/file-changes/components/context/EventsContext.js:152:45)\n    at tryCatch (webpack-internal:///./node_modules/regenerator-runtime/runtime.js:45:40)\n    at Generator.invoke [as _invoke] (webpack-internal:///./node_modules/regenerator-runtime/runtime.js:271:22)\n    at Generator.prototype.<computed> [as next] (webpack-internal:///./node_modules/regenerator-runtime/runtime.js:97:21)\n    at asyncGeneratorStep (webpack-internal:///./node_modules/@babel/runtime/helpers/asyncToGenerator.js:3:24)\n    at _next (webpack-internal:///./node_modules/@babel/runtime/helpers/asyncToGenerator.js:25:9)",
        "trace": null,
        "code": null
    }
]
Resource errors None

Files Monitor → Deleted Files

Page screenshot: Files Monitor → Deleted Files
URL /wp-admin/admin.php?page=wfcm-file-changes&tab=deleted-files
Aspect menu-item-tab
HTTP status 200
Load time 0.221 s
Memory usage 2.74 MiB
JS errors 
[
    {
        "message": "TypeError: Cannot read property 'length' of undefined\n    at EventsProvider._callee$ (webpack-internal:///./assets/js/src/file-changes/components/context/EventsContext.js:152:45)\n    at tryCatch (webpack-internal:///./node_modules/regenerator-runtime/runtime.js:45:40)\n    at Generator.invoke [as _invoke] (webpack-internal:///./node_modules/regenerator-runtime/runtime.js:271:22)\n    at Generator.prototype.<computed> [as next] (webpack-internal:///./node_modules/regenerator-runtime/runtime.js:97:21)\n    at asyncGeneratorStep (webpack-internal:///./node_modules/@babel/runtime/helpers/asyncToGenerator.js:3:24)\n    at _next (webpack-internal:///./node_modules/@babel/runtime/helpers/asyncToGenerator.js:25:9)",
        "trace": null,
        "code": null
    }
]
Resource errors None

Files Monitor → Settings

Page screenshot: Files Monitor → Settings
URL /wp-admin/admin.php?page=wfcm-settings
Aspect menu-item
HTTP status 200
Load time 0.221 s
Memory usage 3.05 MiB
JS errors None
Resource errors None

Files Monitor → Help & About

Page screenshot: Files Monitor → Help & About
URL /wp-admin/admin.php?page=wfcm-about
Aspect menu-item
HTTP status 200
Load time 0.223 s
Memory usage 2.84 MiB
JS errors None
Resource errors None

Files Monitor → Help & About → About

Page screenshot: Files Monitor → Help & About → About
URL /wp-admin/admin.php?page=wfcm-about&tab=about
Aspect menu-item-tab
HTTP status 200
Load time 0.218 s
Memory usage 2.79 MiB
JS errors None
Resource errors None

Files Monitor → Help & About → System Info

Page screenshot: Files Monitor → Help & About → System Info
URL /wp-admin/admin.php?page=wfcm-about&tab=system-info
Aspect menu-item-tab
HTTP status 200
Load time 0.247 s
Memory usage 2.77 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.230 s
Memory usage 2.65 MiB
JS errors None
Resource errors None

Benchmark

URL Load time Memory usage
Inactive Active Change Inactive Active Change
/wp-admin/index.php0.411 s0.274 s-0.137 s2.79 MiB2.88 MiB+ 87.9 KiB
/wp-admin/edit.php0.185 s0.287 s+0.102 s2.84 MiB2.93 MiB+ 92.36 KiB
/wp-admin/post-new.php0.804 s0.935 s+0.131 s4.93 MiB5.08 MiB+ 148.88 KiB
/wp-admin/upload.php0.579 s0.367 s-0.212 s2.67 MiB2.75 MiB+ 87.39 KiB
/wp-admin/options-writing.php0.184 s0.205 s+0.021 s2.68 MiB2.74 MiB+ 57.24 KiB
/wp-admin/media-new.php0.197 s0.201 s+0.004 s2.65 MiB2.73 MiB+ 88.81 KiB
/wp-admin/edit-tags.php?taxonomy=category0.188 s0.182 s-0.006 s2.68 MiB2.83 MiB+ 153.72 KiB
/wp-admin/post-new.php?post_type=page0.635 s0.913 s+0.278 s4.92 MiB5.06 MiB+ 143.84 KiB
/wp-admin/options-discussion.php0.194 s0.262 s+0.068 s2.65 MiB2.74 MiB+ 90.06 KiB
/wp-admin/edit-comments.php0.200 s0.209 s+0.009 s2.75 MiB2.84 MiB+ 89.95 KiB
/0.409 s0.227 s-0.182 s2.61 MiB2.65 MiB+ 40.49 KiB
Average 0.362 s0.369 s+0.007 s3.11 MiB3.2 MiB+ 98.24 KiB

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.

Options wp_options 3

Custom Post Types 1

ID Name
wfcm_file_eventFile Change Events

PHP Error Log

The log file is empty.

See also: All tests for this plugin, How to Hide Melapress File Monitor Admin Menus