WordPress.com Editing Toolkit 3.11821

Does WordPress.com Editing Toolkit work with WordPress 5.8 and PHP 7.4.8? A smoke test was performed on .

Summary

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

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

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

Environment
WordPress version5.8
PHP version7.4.8
MySQL version8.0.21
PHP memory limit256M
Plugin Info
Last updated
Active installs 100,000+
WordPress.org page https://wordpress.org/plugins/full-site-editing/
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=full-site-editing%2Ffull-site-editing-plugin.php&plugin_status=all&paged=1&s&_wpnonce=1c0dc8bd73
Aspect after-activation
HTTP status 200
Load time 0.548 s
Memory usage 3.24 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.228 s
Memory usage 3.03 MiB
JS errors None
Resource errors None

Widgets ‹ Test site — WordPress

Page screenshot: Widgets ‹ Test site — WordPress
URL /wp-admin/widgets.php
Aspect new-sidebar-widgets
HTTP status 200
Load time 2.794 s
Memory usage 4.68 MiB
JS errors None
Resource errors None

Benchmark

URL Load time Memory usage
Inactive Active Change Inactive Active Change
/wp-admin/index.php0.338 s0.305 s-0.033 s3.08 MiB3.21 MiB+ 135.1 KiB
/wp-admin/edit.php0.188 s0.241 s+0.053 s3.11 MiB3.31 MiB+ 200.52 KiB
/wp-admin/post-new.php1.344 s2.638 s+1.294 s5.27 MiB5.49 MiB+ 230.86 KiB
/wp-admin/upload.php0.602 s0.373 s-0.229 s3.03 MiB3.16 MiB+ 135.62 KiB
/wp-admin/options-writing.php0.178 s0.171 s-0.007 s3.02 MiB3.14 MiB+ 120.11 KiB
/wp-admin/media-new.php0.255 s0.217 s-0.038 s3.01 MiB3.14 MiB+ 137.35 KiB
/wp-admin/edit-tags.php?taxonomy=category0.203 s0.199 s-0.004 s3.04 MiB3.17 MiB+ 136.9 KiB
/wp-admin/post-new.php?post_type=page1.177 s6.041 s+4.864 s5.26 MiB10.42 MiB+ 5.16 MiB
/wp-admin/options-discussion.php0.238 s0.474 s+0.236 s3 MiB3.14 MiB+ 136.62 KiB
/wp-admin/edit-comments.php0.220 s0.248 s+0.028 s3.04 MiB3.17 MiB+ 134.84 KiB
/0.408 s0.270 s-0.138 s2.91 MiB3.03 MiB+ 123.88 KiB
Average 0.468 s1.016 s+0.548 s3.43 MiB4.04 MiB+ 616.35 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
Sass
TypeScript
Language % Lines of code Comment lines Files
PHP34.7%6,1702,93459
JavaScript34.0%6,061680105
Sass16.1%2,86412946
TypeScript10.2%1,80811844
Markdown3.5%61907
JSON0.9%15802
SVG0.6%10204
CSS0.1%2241
Total 17,804 3,865 268

PHP Code Analysis | More results »

Lines of code 5,765
Total complexity 1,002
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 92

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 1

Sidebar Widgets 1

ID Name
wpcom-mailerliteMailerlite subscriber popup

PHP Error Log 9 lines

[27-Jul-2021 20:41:12 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
[27-Jul-2021 20:41:12 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
[27-Jul-2021 20:41:12 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
[27-Jul-2021 20:41:16 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
[27-Jul-2021 20:41:16 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
[27-Jul-2021 20:41:16 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
[27-Jul-2021 20:41:24 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
[27-Jul-2021 20:41:24 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
[27-Jul-2021 20:41:24 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
See also: All tests for this plugin