WordPress.com Editing Toolkit 3.10516

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

Summary

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

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

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

Environment
WordPress version5.7.2
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=c7620bdc82
Aspect after-activation
HTTP status 200
Load time 0.475 s
Memory usage 2.92 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.358 s
Memory usage 2.78 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 1.378 s
Memory usage 2.98 MiB
JS errors None
Resource errors None

Benchmark

URL Load time Memory usage
Inactive Active Change Inactive Active Change
/wp-admin/index.php0.764 s0.464 s-0.300 s2.82 MiB2.97 MiB+ 150.07 KiB
/wp-admin/edit.php0.463 s0.360 s-0.103 s2.86 MiB3 MiB+ 138.28 KiB
/wp-admin/post-new.php1.509 s3.921 s+2.412 s5.02 MiB5.44 MiB+ 421.3 KiB
/wp-admin/upload.php0.520 s0.720 s+0.200 s2.7 MiB2.9 MiB+ 214.22 KiB
/wp-admin/options-writing.php0.283 s0.306 s+0.023 s2.71 MiB2.89 MiB+ 183.08 KiB
/wp-admin/media-new.php0.343 s0.298 s-0.045 s2.67 MiB2.82 MiB+ 151.27 KiB
/wp-admin/edit-tags.php?taxonomy=category0.328 s0.350 s+0.022 s2.77 MiB2.92 MiB+ 153.12 KiB
/wp-admin/post-new.php?post_type=page1.277 s9.324 s+8.047 s5.01 MiB10.32 MiB+ 5.31 MiB
/wp-admin/options-discussion.php0.437 s0.695 s+0.258 s2.67 MiB2.82 MiB+ 151.59 KiB
/wp-admin/edit-comments.php0.352 s0.389 s+0.037 s2.78 MiB2.92 MiB+ 150.43 KiB
/0.717 s0.474 s-0.243 s2.65 MiB2.78 MiB+ 129.21 KiB
Average 0.636 s1.573 s+0.937 s3.15 MiB3.8 MiB+ 661.5 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.9%6,0752,91859
JavaScript32.7%5,6791,059103
Sass16.4%2,84412947
TypeScript10.8%1,88431445
Markdown3.6%61907
JSON0.9%15802
SVG0.6%10204
CSS0.1%2241
Total 17,383 4,424 268

PHP Code Analysis | More results »

Lines of code 5,678
Total complexity 960
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 215
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 6 lines

[12-Jul-2021 19:51:17 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 5313
[12-Jul-2021 19:51:17 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 5313
[12-Jul-2021 19:51:17 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 5313
[12-Jul-2021 19:51:23 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 5313
[12-Jul-2021 19:51:23 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 5313
[12-Jul-2021 19:51:23 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 5313
See also: All tests for this plugin