Does WordPress.com Editing Toolkit work with WordPress 5.8 and PHP 7.4.8? A smoke test was performed on .
9 | PHP notices |
No JavaScript exceptions | |
All test pages loaded successfully | |
No resource errors |
Memory usage: 616.35 KiB
The average PHP memory usage increased by this amount after activating by the plugin.
Page speed impact:
0.533 seconds
The average page load time increased by this amount after activating the plugin.
WordPress version | 5.8 |
---|---|
PHP version | 7.4.8 |
MySQL version | 8.0.21 |
PHP memory limit | 256M |
Last updated | |
---|---|
Active installs | 100,000+ |
WordPress.org page | https://wordpress.org/plugins/full-site-editing/ |
Badges |
Get badge code |
URL | /wp-admin/plugins.php?plugin_status=all&paged=1&s |
---|---|
Requested URL | /wp-admin/plugins.php?action=activate&plugin=full-site-editing%2Ffull-site-editing-plugin.php&plugin_status=all&paged=1&s&_wpnonce=2b5036e122 |
Aspect | after-activation |
HTTP status | 200 |
Load time | 0.301 s |
Memory usage | 3.24 MiB |
JS errors | None |
Resource errors | None |
URL | / |
---|---|
Aspect | front-page |
HTTP status | 200 |
Load time | 0.231 s |
Memory usage | 3.03 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/widgets.php |
---|---|
Aspect | new-sidebar-widgets |
HTTP status | 200 |
Load time | 1.945 s |
Memory usage | 4.68 MiB |
JS errors | None |
Resource errors | None |
URL | Load time | Memory usage | ||||
---|---|---|---|---|---|---|
Inactive | Active | Change | Inactive | Active | Change | |
/wp-admin/index.php | 0.371 s | 0.237 s | -0.134 s | 3.08 MiB | 3.21 MiB | + 135.1 KiB |
/wp-admin/edit.php | 0.162 s | 0.288 s | +0.126 s | 3.11 MiB | 3.31 MiB | + 200.52 KiB |
/wp-admin/post-new.php | 0.742 s | 2.296 s | +1.554 s | 5.27 MiB | 5.49 MiB | + 230.86 KiB |
/wp-admin/upload.php | 0.521 s | 0.291 s | -0.230 s | 3.03 MiB | 3.16 MiB | + 135.62 KiB |
/wp-admin/options-writing.php | 0.167 s | 0.150 s | -0.017 s | 3.02 MiB | 3.14 MiB | + 120.11 KiB |
/wp-admin/media-new.php | 0.231 s | 0.183 s | -0.048 s | 3.01 MiB | 3.14 MiB | + 137.35 KiB |
/wp-admin/edit-tags.php?taxonomy=category | 0.180 s | 0.171 s | -0.009 s | 3.04 MiB | 3.17 MiB | + 136.9 KiB |
/wp-admin/post-new.php?post_type=page | 0.604 s | 5.046 s | +4.442 s | 5.26 MiB | 10.42 MiB | + 5.16 MiB |
/wp-admin/options-discussion.php | 0.219 s | 0.412 s | +0.193 s | 3 MiB | 3.14 MiB | + 136.62 KiB |
/wp-admin/edit-comments.php | 0.187 s | 0.211 s | +0.024 s | 3.04 MiB | 3.17 MiB | + 134.84 KiB |
/ | 0.243 s | 0.207 s | -0.036 s | 2.91 MiB | 3.03 MiB | + 123.88 KiB |
Average | 0.330 s | 0.863 s | +0.533 s | 3.43 MiB | 4.04 MiB | + 616.35 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 | 34.6% | 6,156 | 2,926 | 59 | |
JavaScript | 34.1% | 6,061 | 680 | 105 | |
Sass | 16.1% | 2,864 | 129 | 46 | |
TypeScript | 10.2% | 1,808 | 118 | 44 | |
Markdown | 3.5% | 619 | 0 | 7 | |
JSON | 0.9% | 158 | 0 | 2 | |
SVG | 0.6% | 102 | 0 | 4 | |
CSS | 0.1% | 22 | 4 | 1 | |
Total | 17,790 | 3,857 | 268 |
Lines of code | 5,751 |
---|---|
Total complexity | 1,001 |
Median class complexity | 13.0 |
Median method complexity | 2.0 |
Most complex class | Newspack_Blocks |
Most complex function | newspack_blocks_render_block_carousel() |
Classes | 30 |
---|---|
Methods | 222 |
Functions | 91 |
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.
wp_options
1ID | Name |
---|---|
wpcom-mailerlite | Mailerlite subscriber popup |
[28-Jul-2021 04:21:43 UTC] PHP Notice: WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. 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.7.0.) in /wp-includes/functions.php on line 5535
[28-Jul-2021 04:21:43 UTC] PHP Notice: WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. 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.7.0.) in /wp-includes/functions.php on line 5535
[28-Jul-2021 04:21:43 UTC] PHP Notice: WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. 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.7.0.) in /wp-includes/functions.php on line 5535
[28-Jul-2021 04:21:47 UTC] PHP Notice: WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. 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.7.0.) in /wp-includes/functions.php on line 5535
[28-Jul-2021 04:21:47 UTC] PHP Notice: WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. 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.7.0.) in /wp-includes/functions.php on line 5535
[28-Jul-2021 04:21:47 UTC] PHP Notice: WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. 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.7.0.) in /wp-includes/functions.php on line 5535
[28-Jul-2021 04:21:53 UTC] PHP Notice: WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. 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.7.0.) in /wp-includes/functions.php on line 5535
[28-Jul-2021 04:21:53 UTC] PHP Notice: WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. 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.7.0.) in /wp-includes/functions.php on line 5535
[28-Jul-2021 04:21:53 UTC] PHP Notice: WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. 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.7.0.) in /wp-includes/functions.php on line 5535