MoonClerk WP Shortcode 1.0.6

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

Summary

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

Memory usage: -13.86 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.5
PHP version7.2.16
MySQL version8.0.15
PHP memory limit256M
Plugin Info
Last updated
Active installs 400+
WordPress.org page https://wordpress.org/plugins/moonclerk-wp-shortcode/
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=moonclerk-wp-shortcode%2Fmoonclerk-wp-shortcode.php&plugin_status=all&paged=1&s&_wpnonce=238c8cf550
Aspect after-activation
HTTP status 200
Load time 0.357 s
Memory usage 3.91 MiB
JS errors None
Resource errors None

Tools → MoonClerk

Page screenshot: Tools → MoonClerk
URL /wp-admin/tools.php?page=moonclerk-wp-shortcode%2Fmoonclerk-wp-shortcode.php
Requested URL /wp-admin/tools.php?page=moonclerk-wp-shortcode/moonclerk-wp-shortcode.php
Aspect menu-item
HTTP status 200
Load time 0.189 s
Memory usage 3.91 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.322 s
Memory usage 3.58 MiB
JS errors None
Resource errors None

Benchmark

URL Load time Memory usage
Inactive Active Change Inactive Active Change
/wp-admin/index.php0.491 s0.304 s-0.187 s3.96 MiB3.97 MiB+ 9.92 KiB
/wp-admin/edit.php0.258 s0.222 s-0.036 s3.99 MiB3.99 MiB+ 4.42 KiB
/wp-admin/post-new.php1.631 s1.968 s+0.337 s5.81 MiB5.82 MiB+ 11.19 KiB
/wp-admin/upload.php0.673 s0.416 s-0.257 s3.82 MiB3.83 MiB+ 3.89 KiB
/wp-admin/options-writing.php0.173 s0.148 s-0.025 s3.9 MiB3.82 MiB- 89.55 KiB
/wp-admin/media-new.php0.201 s0.169 s-0.032 s3.8 MiB3.81 MiB+ 4.06 KiB
/wp-admin/edit-tags.php?taxonomy=category0.198 s0.176 s-0.022 s3.91 MiB3.91 MiB+ 4.97 KiB
/wp-admin/post-new.php?post_type=page1.324 s1.348 s+0.024 s5.8 MiB5.81 MiB+ 4.37 KiB
/wp-admin/options-discussion.php0.256 s0.251 s-0.005 s3.81 MiB3.81 MiB+ 4.38 KiB
/wp-admin/edit-comments.php0.218 s0.194 s-0.024 s3.91 MiB3.92 MiB+ 3.27 KiB
/0.387 s0.201 s-0.186 s3.69 MiB3.58 MiB- 113.41 KiB
Average 0.528 s0.491 s-0.038 s4.22 MiB4.21 MiB- 13.86 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.

No new entries found.

PHP Error Log 16 lines

[16-Aug-2020 00:33:33 UTC] PHP Notice:  add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be an integer representing menu position. 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.3.0.) in /wp-includes/functions.php on line 5225
[16-Aug-2020 00:33:34 UTC] PHP Notice:  add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be an integer representing menu position. 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.3.0.) in /wp-includes/functions.php on line 5225
[16-Aug-2020 00:33:34 UTC] PHP Notice:  add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be an integer representing menu position. 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.3.0.) in /wp-includes/functions.php on line 5225
[16-Aug-2020 00:33:35 UTC] PHP Notice:  add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be an integer representing menu position. 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.3.0.) in /wp-includes/functions.php on line 5225
[16-Aug-2020 00:33:36 UTC] PHP Notice:  add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be an integer representing menu position. 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.3.0.) in /wp-includes/functions.php on line 5225
[16-Aug-2020 00:33:36 UTC] PHP Notice:  add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be an integer representing menu position. 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.3.0.) in /wp-includes/functions.php on line 5225
[16-Aug-2020 00:33:38 UTC] PHP Notice:  add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be an integer representing menu position. 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.3.0.) in /wp-includes/functions.php on line 5225
[16-Aug-2020 00:33:38 UTC] PHP Notice:  add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be an integer representing menu position. 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.3.0.) in /wp-includes/functions.php on line 5225
[16-Aug-2020 00:33:38 UTC] PHP Notice:  add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be an integer representing menu position. 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.3.0.) in /wp-includes/functions.php on line 5225
[16-Aug-2020 00:33:39 UTC] PHP Notice:  add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be an integer representing menu position. 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.3.0.) in /wp-includes/functions.php on line 5225
[16-Aug-2020 00:33:39 UTC] PHP Notice:  add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be an integer representing menu position. 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.3.0.) in /wp-includes/functions.php on line 5225
[16-Aug-2020 00:33:41 UTC] PHP Notice:  add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be an integer representing menu position. 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.3.0.) in /wp-includes/functions.php on line 5225
[16-Aug-2020 00:33:41 UTC] PHP Notice:  add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be an integer representing menu position. 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.3.0.) in /wp-includes/functions.php on line 5225
[16-Aug-2020 00:33:41 UTC] PHP Notice:  add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be an integer representing menu position. 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.3.0.) in /wp-includes/functions.php on line 5225
[16-Aug-2020 00:33:42 UTC] PHP Notice:  add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be an integer representing menu position. 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.3.0.) in /wp-includes/functions.php on line 5225
[16-Aug-2020 00:33:42 UTC] PHP Notice:  add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be an integer representing menu position. 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.3.0.) in /wp-includes/functions.php on line 5225
See also: All tests for this plugin, How to Hide the "MoonClerk" Admin Menu