Stionic Core 1.0.21

Does Stionic Core work with WordPress 5.7.1 and PHP 7.4.8? A smoke test was performed on .

Summary

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

Memory usage: 83.48 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.7.1
PHP version7.4.8
MySQL version8.0.21
PHP memory limit256M
Plugin Info
Last updated
Active installs 100+
WordPress.org page https://wordpress.org/plugins/stionic-core/
Badges

WordPress compatibility badge PHP compatibility badge

Get badge code

Pages 9

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=stionic-core%2Fstionic-core.php&plugin_status=all&paged=1&s&_wpnonce=06db578c91
Aspect after-activation
HTTP status 200
Load time 0.253 s
Memory usage 2.83 MiB
JS errors None
Resource errors None

Stionic

Page screenshot: Stionic
URL /wp-admin/admin.php?page=stionic
Aspect menu-item
HTTP status 200
Load time 0.168 s
Memory usage 2.84 MiB
JS errors None
Resource errors None

Stionic → Categories

Page screenshot: Stionic → Categories
URL /wp-admin/admin.php?page=stionic-categories
Aspect menu-item
HTTP status 200
Load time 0.192 s
Memory usage 2.8 MiB
JS errors None
Resource errors None

Stionic → Media

Page screenshot: Stionic → Media
URL /wp-admin/admin.php?page=stionic-media
Aspect menu-item
HTTP status 200
Load time 0.139 s
Memory usage 2.79 MiB
JS errors None
Resource errors None

Stionic → DeepLinks

Page screenshot: Stionic → DeepLinks
URL /wp-admin/admin.php?page=stionic-deeplinks
Aspect menu-item
HTTP status 200
Load time 0.147 s
Memory usage 2.8 MiB
JS errors None
Resource errors None

Stionic → OneSignal

Page screenshot: Stionic → OneSignal
URL /wp-admin/admin.php?page=stionic-onesignal
Aspect menu-item
HTTP status 200
Load time 0.146 s
Memory usage 2.8 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.242 s
Memory usage 2.7 MiB
JS errors None
Resource errors None

Add New Post ‹ Test site — WordPress

Page screenshot: Add New Post ‹ Test site — WordPress
URL /wp-admin/post-new.php
Aspect new-meta-boxes
HTTP status 200
Load time 0.820 s
Memory usage 5.23 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 0.776 s
Memory usage 5.21 MiB
JS errors None
Resource errors None

Benchmark

URL Load time Memory usage
Inactive Active Change Inactive Active Change
/wp-admin/index.php0.279 s0.568 s+0.289 s2.82 MiB2.88 MiB+ 61.59 KiB
/wp-admin/edit.php0.187 s0.220 s+0.033 s2.86 MiB2.92 MiB+ 62.02 KiB
/wp-admin/post-new.php1.002 s0.981 s-0.021 s5.02 MiB5.23 MiB+ 214.38 KiB
/wp-admin/upload.php0.506 s0.302 s-0.204 s2.7 MiB2.75 MiB+ 59.05 KiB
/wp-admin/options-writing.php0.251 s0.154 s-0.097 s2.71 MiB2.74 MiB+ 27.39 KiB
/wp-admin/media-new.php0.229 s0.201 s-0.028 s2.67 MiB2.73 MiB+ 59.59 KiB
/wp-admin/edit-tags.php?taxonomy=category0.180 s0.195 s+0.015 s2.77 MiB2.83 MiB+ 60.49 KiB
/wp-admin/post-new.php?post_type=page1.204 s0.774 s-0.430 s5.01 MiB5.21 MiB+ 210.6 KiB
/wp-admin/options-discussion.php0.329 s0.281 s-0.048 s2.67 MiB2.73 MiB+ 59.9 KiB
/wp-admin/edit-comments.php0.243 s0.226 s-0.017 s2.78 MiB2.83 MiB+ 59.44 KiB
/0.260 s0.220 s-0.040 s2.65 MiB2.7 MiB+ 43.84 KiB
Average 0.425 s0.375 s-0.050 s3.15 MiB3.23 MiB+ 83.48 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
JavaScript
Language % Lines of code Comment lines Files
PHP82.6%1,56413520
JavaScript11.4%21514
CSS6.0%11403
Total 1,893 136 27

PHP Code Analysis | More results »

Lines of code 1,164
Total complexity 249
Median class complexity 11.5
Median method complexity 1.0
Most complex class Stionic_Admin_Metaboxes
Most complex function Stionic_Admin_Metaboxes::stionic_save_post()
Classes 14
Methods 64
Functions 2

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 2

Meta Boxes

{
    "post": {
        "stionic-application": {
            "title": "Stionic application",
            "context": "side"
        }
    },
    "page": {
        "stionic-application": {
            "title": "Stionic application",
            "context": "side"
        }
    }
}

PHP Error Log 28 lines

[19-Apr-2021 20:55:49 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wp/v2/m_config</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. 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.5.0.) in /wp-includes/functions.php on line 5313
[19-Apr-2021 20:55:49 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wp/v2/m_categories</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. 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.5.0.) in /wp-includes/functions.php on line 5313
[19-Apr-2021 20:55:49 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wp/v2/m_posts</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. 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.5.0.) in /wp-includes/functions.php on line 5313
[19-Apr-2021 20:55:49 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wp/v2/m_comments/(?P<post>[\d]+)</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. 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.5.0.) in /wp-includes/functions.php on line 5313
[19-Apr-2021 20:55:49 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wp/v2/m_pages</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. 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.5.0.) in /wp-includes/functions.php on line 5313
[19-Apr-2021 20:55:49 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wp/v2/m_tools/final_url</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. 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.5.0.) in /wp-includes/functions.php on line 5313
[19-Apr-2021 20:55:49 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wp/v2/m_tools/deeplinks</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. 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.5.0.) in /wp-includes/functions.php on line 5313
[19-Apr-2021 20:55:52 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wp/v2/m_config</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. 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.5.0.) in /wp-includes/functions.php on line 5313
[19-Apr-2021 20:55:52 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wp/v2/m_categories</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. 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.5.0.) in /wp-includes/functions.php on line 5313
[19-Apr-2021 20:55:52 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wp/v2/m_posts</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. 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.5.0.) in /wp-includes/functions.php on line 5313
[19-Apr-2021 20:55:52 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wp/v2/m_comments/(?P<post>[\d]+)</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. 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.5.0.) in /wp-includes/functions.php on line 5313
[19-Apr-2021 20:55:52 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wp/v2/m_pages</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. 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.5.0.) in /wp-includes/functions.php on line 5313
[19-Apr-2021 20:55:52 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wp/v2/m_tools/final_url</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. 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.5.0.) in /wp-includes/functions.php on line 5313
[19-Apr-2021 20:55:52 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wp/v2/m_tools/deeplinks</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. 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.5.0.) in /wp-includes/functions.php on line 5313
[19-Apr-2021 20:55:55 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wp/v2/m_config</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. 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.5.0.) in /wp-includes/functions.php on line 5313
[19-Apr-2021 20:55:55 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wp/v2/m_categories</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. 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.5.0.) in /wp-includes/functions.php on line 5313
[19-Apr-2021 20:55:55 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wp/v2/m_posts</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. 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.5.0.) in /wp-includes/functions.php on line 5313
[19-Apr-2021 20:55:55 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wp/v2/m_comments/(?P<post>[\d]+)</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. 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.5.0.) in /wp-includes/functions.php on line 5313
[19-Apr-2021 20:55:55 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wp/v2/m_pages</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. 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.5.0.) in /wp-includes/functions.php on line 5313
[19-Apr-2021 20:55:55 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wp/v2/m_tools/final_url</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. 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.5.0.) in /wp-includes/functions.php on line 5313
[19-Apr-2021 20:55:55 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wp/v2/m_tools/deeplinks</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. 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.5.0.) in /wp-includes/functions.php on line 5313
[19-Apr-2021 20:55:57 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wp/v2/m_config</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. 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.5.0.) in /wp-includes/functions.php on line 5313
[19-Apr-2021 20:55:57 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wp/v2/m_categories</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. 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.5.0.) in /wp-includes/functions.php on line 5313
[19-Apr-2021 20:55:57 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wp/v2/m_posts</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. 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.5.0.) in /wp-includes/functions.php on line 5313
[19-Apr-2021 20:55:57 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wp/v2/m_comments/(?P<post>[\d]+)</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. 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.5.0.) in /wp-includes/functions.php on line 5313
[19-Apr-2021 20:55:57 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wp/v2/m_pages</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. 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.5.0.) in /wp-includes/functions.php on line 5313
[19-Apr-2021 20:55:57 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wp/v2/m_tools/final_url</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. 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.5.0.) in /wp-includes/functions.php on line 5313
[19-Apr-2021 20:55:57 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wp/v2/m_tools/deeplinks</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. 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.5.0.) in /wp-includes/functions.php on line 5313
See also: All tests for this plugin, How to Hide Stionic Core Admin Menus and Meta Boxes