WordPress.com Editing Toolkit 3.6007

Does WordPress.com Editing Toolkit work with WordPress 5.7.1 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: 641.56 KiB
The average PHP memory usage increased by this amount after activating by the plugin.

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

Environment
WordPress version5.7.1
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=280e0a5fbf
Aspect after-activation
HTTP status 200
Load time 0.392 s
Memory usage 2.93 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.266 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 0.837 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.254 s0.266 s+0.012 s2.82 MiB2.97 MiB+ 149.82 KiB
/wp-admin/edit.php0.177 s0.204 s+0.027 s2.86 MiB3 MiB+ 137.69 KiB
/wp-admin/post-new.php0.833 s2.326 s+1.493 s5.03 MiB5.44 MiB+ 421.03 KiB
/wp-admin/upload.php0.677 s0.261 s-0.416 s2.7 MiB2.84 MiB+ 149.09 KiB
/wp-admin/options-writing.php0.272 s0.158 s-0.114 s2.71 MiB2.86 MiB+ 146.84 KiB
/wp-admin/media-new.php0.213 s0.287 s+0.074 s2.67 MiB2.82 MiB+ 149.26 KiB
/wp-admin/edit-tags.php?taxonomy=category0.189 s0.244 s+0.055 s2.77 MiB2.92 MiB+ 152.04 KiB
/wp-admin/post-new.php?post_type=page1.028 s5.106 s+4.078 s5.01 MiB10.21 MiB+ 5.2 MiB
/wp-admin/options-discussion.php0.280 s0.292 s+0.012 s2.68 MiB2.82 MiB+ 150.82 KiB
/wp-admin/edit-comments.php0.219 s0.234 s+0.015 s2.78 MiB2.92 MiB+ 149.66 KiB
/0.351 s0.237 s-0.114 s2.65 MiB2.78 MiB+ 129.66 KiB
Average 0.408 s0.874 s+0.466 s3.15 MiB3.78 MiB+ 641.56 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,9462,86758
JavaScript32.9%5,6571,055103
Sass16.4%2,83012647
TypeScript10.9%1,87631645
Markdown3.6%61607
JSON0.9%15802
SVG0.6%10204
CSS0.1%2241
Total 17,207 4,368 267

PHP Code Analysis | More results »

Lines of code 5,549
Total complexity 933
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 207
Functions 93

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

[07-May-2021 06:28:25 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
[07-May-2021 06:28:25 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
[07-May-2021 06:28:25 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
[07-May-2021 06:28:29 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
[07-May-2021 06:28:29 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
[07-May-2021 06:28:29 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