Does MoonClerk WP Shortcode work with WordPress 5.7.2 and PHP 7.4.8? A smoke test was performed on .
| 16 | PHP notices |
| No JavaScript exceptions | |
| All test pages loaded successfully | |
| No resource errors |
Memory usage: 3.05 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.
| WordPress version | 5.7.2 |
|---|---|
| PHP version | 7.4.8 |
| MySQL version | 8.0.21 |
| PHP memory limit | 256M |
| Last updated | |
|---|---|
| Active installs | 400+ |
| WordPress.org page | https://wordpress.org/plugins/moonclerk-wp-shortcode/ |
| Badges |
|
| 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=73b5492b99 |
| Aspect | after-activation |
| HTTP status | 200 |
| Load time | 0.218 s |
| Memory usage | 2.72 MiB |
| JS errors | None |
| Resource errors | None |
| 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.190 s |
| Memory usage | 2.72 MiB |
| JS errors | None |
| Resource errors | None |
| URL | / |
|---|---|
| Aspect | front-page |
| HTTP status | 200 |
| Load time | 0.167 s |
| Memory usage | 2.65 MiB |
| JS errors | None |
| Resource errors | None |
| URL | Load time | Memory usage | ||||
|---|---|---|---|---|---|---|
| Inactive | Active | Change | Inactive | Active | Change | |
| /wp-admin/index.php | 0.260 s | 0.253 s | -0.007 s | 2.82 MiB | 2.83 MiB | + 8.16 KiB |
| /wp-admin/edit.php | 0.195 s | 0.190 s | -0.005 s | 2.86 MiB | 2.87 MiB | + 8.16 KiB |
| /wp-admin/post-new.php | 0.875 s | 1.002 s | +0.127 s | 5.02 MiB | 5.04 MiB | + 20.52 KiB |
| /wp-admin/upload.php | 0.505 s | 0.468 s | -0.037 s | 2.7 MiB | 2.7 MiB | + 3.63 KiB |
| /wp-admin/options-writing.php | 0.146 s | 0.161 s | +0.015 s | 2.71 MiB | 2.68 MiB | - 28.4 KiB |
| /wp-admin/media-new.php | 0.277 s | 0.179 s | -0.098 s | 2.67 MiB | 2.68 MiB | + 3.8 KiB |
| /wp-admin/edit-tags.php?taxonomy=category | 0.187 s | 0.177 s | -0.010 s | 2.77 MiB | 2.78 MiB | + 4.7 KiB |
| /wp-admin/post-new.php?post_type=page | 1.725 s | 0.709 s | -1.016 s | 5.01 MiB | 5.01 MiB | + 4.1 KiB |
| /wp-admin/options-discussion.php | 0.244 s | 0.197 s | -0.047 s | 2.67 MiB | 2.68 MiB | + 4.11 KiB |
| /wp-admin/edit-comments.php | 0.209 s | 0.209 s | +0.000 s | 2.78 MiB | 2.78 MiB | + 3.01 KiB |
| / | 0.305 s | 0.211 s | -0.094 s | 2.65 MiB | 2.65 MiB | + 1.78 KiB |
| Average | 0.448 s | 0.341 s | -0.107 s | 3.15 MiB | 3.15 MiB | + 3.05 KiB |
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.
| Language | % | Lines of code | Comment lines | Files | |
|---|---|---|---|---|---|
| PHP | 74.8% | 86 | 52 | 3 | |
| Markdown | 17.4% | 20 | 0 | 1 | |
| JavaScript | 7.8% | 9 | 3 | 1 | |
| Total | 115 | 55 | 5 | ||
| Lines of code | 64 |
|---|---|
| Total complexity | 12 |
| Median class complexity | 5.0 |
| Median method complexity | 1.0 |
| Most complex class | moonClerk_wp |
| Most complex function | moonClerk_short() |
| Classes | 1 |
|---|---|
| Methods | 5 |
| Functions | 2 |
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.
[16-May-2021 12:35:57 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 5313
[16-May-2021 12:35:58 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 5313
[16-May-2021 12:35:58 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 5313
[16-May-2021 12:35:59 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 5313
[16-May-2021 12:35:59 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 5313
[16-May-2021 12:36:00 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 5313
[16-May-2021 12:36:02 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 5313
[16-May-2021 12:36:02 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 5313
[16-May-2021 12:36:03 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 5313
[16-May-2021 12:36:03 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 5313
[16-May-2021 12:36:03 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 5313
[16-May-2021 12:36:05 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 5313
[16-May-2021 12:36:05 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 5313
[16-May-2021 12:36:05 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 5313
[16-May-2021 12:36:06 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 5313
[16-May-2021 12:36:06 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 5313