WordPress.com Editing Toolkit 3.11861

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.533 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=2b5036e122
Aspect after-activation
HTTP status 200
Load time 0.301 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.231 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 1.945 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.371 s0.237 s-0.134 s3.08 MiB3.21 MiB+ 135.1 KiB
/wp-admin/edit.php0.162 s0.288 s+0.126 s3.11 MiB3.31 MiB+ 200.52 KiB
/wp-admin/post-new.php0.742 s2.296 s+1.554 s5.27 MiB5.49 MiB+ 230.86 KiB
/wp-admin/upload.php0.521 s0.291 s-0.230 s3.03 MiB3.16 MiB+ 135.62 KiB
/wp-admin/options-writing.php0.167 s0.150 s-0.017 s3.02 MiB3.14 MiB+ 120.11 KiB
/wp-admin/media-new.php0.231 s0.183 s-0.048 s3.01 MiB3.14 MiB+ 137.35 KiB
/wp-admin/edit-tags.php?taxonomy=category0.180 s0.171 s-0.009 s3.04 MiB3.17 MiB+ 136.9 KiB
/wp-admin/post-new.php?post_type=page0.604 s5.046 s+4.442 s5.26 MiB10.42 MiB+ 5.16 MiB
/wp-admin/options-discussion.php0.219 s0.412 s+0.193 s3 MiB3.14 MiB+ 136.62 KiB
/wp-admin/edit-comments.php0.187 s0.211 s+0.024 s3.04 MiB3.17 MiB+ 134.84 KiB
/0.243 s0.207 s-0.036 s2.91 MiB3.03 MiB+ 123.88 KiB
Average 0.330 s0.863 s+0.533 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.6%6,1562,92659
JavaScript34.1%6,061680105
Sass16.1%2,86412946
TypeScript10.2%1,80811844
Markdown3.5%61907
JSON0.9%15802
SVG0.6%10204
CSS0.1%2241
Total 17,790 3,857 268

PHP Code Analysis | More results »

Lines of code 5,751
Total complexity 1,001
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 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 9 lines

[28-Jul-2021 04:21:43 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
[28-Jul-2021 04:21:43 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
[28-Jul-2021 04:21:43 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
[28-Jul-2021 04:21:47 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
[28-Jul-2021 04:21:47 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
[28-Jul-2021 04:21:47 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
[28-Jul-2021 04:21:53 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
[28-Jul-2021 04:21:53 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
[28-Jul-2021 04:21:53 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