WordPress.com Editing Toolkit 3.10498

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.549 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=fe63bd2630
Aspect after-activation
HTTP status 200
Load time 0.396 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.215 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.814 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.253 s0.271 s+0.018 s2.82 MiB2.97 MiB+ 150.07 KiB
/wp-admin/edit.php0.172 s0.192 s+0.020 s2.86 MiB3 MiB+ 138.28 KiB
/wp-admin/post-new.php0.878 s2.545 s+1.667 s5.02 MiB5.44 MiB+ 421.3 KiB
/wp-admin/upload.php0.468 s0.294 s-0.174 s2.7 MiB2.9 MiB+ 214.22 KiB
/wp-admin/options-writing.php0.231 s0.261 s+0.030 s2.71 MiB2.89 MiB+ 183.08 KiB
/wp-admin/media-new.php0.209 s0.253 s+0.044 s2.67 MiB2.82 MiB+ 151.27 KiB
/wp-admin/edit-tags.php?taxonomy=category0.190 s0.197 s+0.007 s2.77 MiB2.92 MiB+ 153.12 KiB
/wp-admin/post-new.php?post_type=page1.119 s5.484 s+4.365 s5.01 MiB10.32 MiB+ 5.31 MiB
/wp-admin/options-discussion.php0.306 s0.425 s+0.119 s2.67 MiB2.82 MiB+ 151.59 KiB
/wp-admin/edit-comments.php0.232 s0.228 s-0.004 s2.78 MiB2.92 MiB+ 150.43 KiB
/0.275 s0.223 s-0.052 s2.65 MiB2.78 MiB+ 129.21 KiB
Average 0.394 s0.943 s+0.549 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,0602,90059
JavaScript32.7%5,6781,059103
Sass16.4%2,84812947
TypeScript10.8%1,88431445
Markdown3.6%61907
JSON0.9%15802
SVG0.6%10204
CSS0.1%2241
Total 17,371 4,406 268

PHP Code Analysis | More results »

Lines of code 5,663
Total complexity 955
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 213
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 16:13:27 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 16:13:27 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 16:13:27 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 16:13:32 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 16:13:32 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 16:13:32 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