WordPress.com Editing Toolkit 3.7046

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: 660.25 KiB
The average PHP memory usage increased by this amount after activating by the plugin.

Page speed impact: 0.578 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=03876c98db
Aspect after-activation
HTTP status 200
Load time 0.315 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.322 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.196 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.267 s0.283 s+0.016 s2.82 MiB2.97 MiB+ 149.11 KiB
/wp-admin/edit.php0.179 s0.222 s+0.043 s2.86 MiB3 MiB+ 136.98 KiB
/wp-admin/post-new.php0.935 s1.803 s+0.868 s5.02 MiB5.43 MiB+ 420.32 KiB
/wp-admin/upload.php0.492 s0.301 s-0.191 s2.7 MiB2.9 MiB+ 212.38 KiB
/wp-admin/options-writing.php0.168 s0.187 s+0.019 s2.71 MiB2.89 MiB+ 181.6 KiB
/wp-admin/media-new.php0.275 s0.192 s-0.083 s2.67 MiB2.82 MiB+ 148.55 KiB
/wp-admin/edit-tags.php?taxonomy=category0.226 s0.297 s+0.071 s2.77 MiB2.92 MiB+ 151.33 KiB
/wp-admin/post-new.php?post_type=page0.973 s6.504 s+5.531 s5.01 MiB10.32 MiB+ 5.31 MiB
/wp-admin/options-discussion.php0.314 s0.417 s+0.103 s2.67 MiB2.82 MiB+ 150.11 KiB
/wp-admin/edit-comments.php0.254 s0.238 s-0.016 s2.78 MiB2.92 MiB+ 148.95 KiB
/0.300 s0.299 s-0.001 s2.65 MiB2.78 MiB+ 128.95 KiB
Average 0.398 s0.977 s+0.578 s3.15 MiB3.8 MiB+ 660.25 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.6%5,9712,84958
JavaScript32.9%5,6791,062103
Sass16.4%2,82912647
TypeScript11.0%1,89131645
Markdown3.6%61607
JSON0.9%15802
SVG0.6%10204
CSS0.1%2241
Total 17,268 4,357 267

PHP Code Analysis | More results »

Lines of code 5,574
Total complexity 937
Median class complexity 13.0
Median method complexity 2.0
Most complex class Newspack_Blocks
Most complex function newspack_blocks_render_block_carousel()
Classes 29
Methods 208
Functions 91

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

[21-May-2021 00:26:05 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
[21-May-2021 00:26:05 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
[21-May-2021 00:26:05 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
[21-May-2021 00:26:09 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
[21-May-2021 00:26:09 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
[21-May-2021 00:26:09 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