Quentn WP 1.0.9

Does Quentn WP work with WordPress 5.5 and PHP 7.2.16? A smoke test was performed on .

Summary

Errors
5PHP warnings
15PHP notices
No JavaScript exceptions
All test pages loaded successfully
No resource errors
Performance

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

Page speed impact: 0.088 seconds
The average page load time increased by this amount after activating the plugin.

Environment
WordPress version5.5
PHP version7.2.16
MySQL version8.0.15
PHP memory limit256M
Plugin Info
Last updated
Active installs 500+
WordPress.org page https://wordpress.org/plugins/quentn-wp/
Badges

WordPress compatibility badge PHP compatibility badge

Get badge code

Pages 8

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=quentn-wp%2Fquentn-wp.php&plugin_status=all&paged=1&s&_wpnonce=5cc791cffe
Aspect after-activation
HTTP status 200
Load time 0.721 s
Memory usage 4.11 MiB
JS errors None
Resource errors None

Quentn

Page screenshot: Quentn
URL /wp-admin/admin.php?page=quentn-dashboard
Aspect menu-item
HTTP status 200
Load time 0.455 s
Memory usage 4.24 MiB
JS errors None
Resource errors None

Quentn → Roles

Page screenshot: Quentn → Roles
URL /wp-admin/admin.php?page=quentn-dashboard&tab=qnentn_tags_selection
Aspect menu-item-tab
HTTP status 200
Load time 0.296 s
Memory usage 4.1 MiB
JS errors None
Resource errors None

Quentn → Web Tracking

Page screenshot: Quentn → Web Tracking
URL /wp-admin/admin.php?page=quentn-dashboard&tab=qnentn_web_tracking_tab
Aspect menu-item-tab
HTTP status 200
Load time 0.274 s
Memory usage 4.1 MiB
JS errors None
Resource errors None

Quentn → Delete User Data

Page screenshot: Quentn → Delete User Data
URL /wp-admin/admin.php?page=quentn-dashboard&tab=qnentn_delete_user_data
Aspect menu-item-tab
HTTP status 200
Load time 0.230 s
Memory usage 4.21 MiB
JS errors None
Resource errors None

Quentn → Access Restrictions

Page screenshot: Quentn → Access Restrictions
URL /wp-admin/admin.php?page=quentn-access-pages-restrictions
Aspect menu-item
HTTP status 200
Load time 0.508 s
Memory usage 4.22 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.375 s
Memory usage 4.13 MiB
JS errors None
Resource errors None

Add New Page ‹ Test site — WordPress

Page screenshot: Add New Page ‹ Test site — WordPress
URL /wp-admin/post-new.php?post_type=page
Aspect new-meta-boxes
HTTP status 200
Load time 1.778 s
Memory usage 6.22 MiB
JS errors None
Resource errors None

Benchmark

URL Load time Memory usage
Inactive Active Change Inactive Active Change
/wp-admin/index.php0.506 s0.426 s-0.080 s3.96 MiB4.23 MiB+ 276.53 KiB
/wp-admin/edit.php0.256 s0.279 s+0.023 s3.99 MiB4.24 MiB+ 254.23 KiB
/wp-admin/post-new.php1.781 s2.427 s+0.646 s5.81 MiB6.22 MiB+ 413.17 KiB
/wp-admin/upload.php0.830 s0.506 s-0.324 s3.82 MiB4.11 MiB+ 295.35 KiB
/wp-admin/options-writing.php0.191 s0.161 s-0.030 s3.9 MiB4.06 MiB+ 164.19 KiB
/wp-admin/media-new.php0.239 s0.199 s-0.040 s3.8 MiB4.06 MiB+ 257.82 KiB
/wp-admin/edit-tags.php?taxonomy=category0.210 s0.189 s-0.021 s3.91 MiB4.11 MiB+ 208.83 KiB
/wp-admin/post-new.php?post_type=page1.605 s2.452 s+0.847 s5.8 MiB6.21 MiB+ 417.91 KiB
/wp-admin/options-discussion.php0.387 s0.425 s+0.038 s3.81 MiB4.07 MiB+ 264.64 KiB
/wp-admin/edit-comments.php0.236 s0.257 s+0.021 s3.91 MiB4.12 MiB+ 207.77 KiB
/0.370 s0.259 s-0.111 s3.69 MiB3.91 MiB+ 217.04 KiB
Average 0.601 s0.689 s+0.088 s4.22 MiB4.48 MiB+ 270.68 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.

Database Tables 2

Options wp_options 2

Meta Boxes

{
    "page": {
        "quentn-access-restriction-meta-box": {
            "title": "Quentn Page Restriction",
            "context": "advanced"
        }
    }
}

PHP Error Log 20 lines

[16-Aug-2020 23:43:56 UTC] PHP Warning:  Invalid argument supplied for foreach() in /wp-content/plugins/quentn-wp/admin/class-quentn-wp-admin.php on line 901
[16-Aug-2020 23:43:56 UTC] PHP Warning:  Invalid argument supplied for foreach() in /wp-content/plugins/quentn-wp/admin/class-quentn-wp-admin.php on line 901
[16-Aug-2020 23:43:56 UTC] PHP Warning:  Invalid argument supplied for foreach() in /wp-content/plugins/quentn-wp/admin/class-quentn-wp-admin.php on line 901
[16-Aug-2020 23:43:56 UTC] PHP Warning:  Invalid argument supplied for foreach() in /wp-content/plugins/quentn-wp/admin/class-quentn-wp-admin.php on line 901
[16-Aug-2020 23:43:56 UTC] PHP Warning:  Invalid argument supplied for foreach() in /wp-content/plugins/quentn-wp/admin/class-quentn-wp-admin.php on line 901
[16-Aug-2020 23:44:01 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5225
[16-Aug-2020 23:44:01 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5225
[16-Aug-2020 23:44:01 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5225
[16-Aug-2020 23:44:01 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5225
[16-Aug-2020 23:44:01 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5225
[16-Aug-2020 23:44:04 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5225
[16-Aug-2020 23:44:04 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5225
[16-Aug-2020 23:44:04 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5225
[16-Aug-2020 23:44:04 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5225
[16-Aug-2020 23:44:04 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5225
[16-Aug-2020 23:44:08 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5225
[16-Aug-2020 23:44:08 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5225
[16-Aug-2020 23:44:08 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5225
[16-Aug-2020 23:44:08 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5225
[16-Aug-2020 23:44:08 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5225
See also: All tests for this plugin, How to Hide Quentn WP Admin Menus and Meta Boxes