WordPress.com Editing Toolkit 3.12084

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

Page speed impact: 0.545 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=3bbb335278
Aspect after-activation
HTTP status 200
Load time 0.304 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.206 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 3.418 s
Memory usage 4.69 MiB
JS errors None
Resource errors None

Benchmark

URL Load time Memory usage
Inactive Active Change Inactive Active Change
/wp-admin/index.php0.313 s0.241 s-0.072 s3.08 MiB3.22 MiB+ 139.81 KiB
/wp-admin/edit.php0.188 s0.193 s+0.005 s3.11 MiB3.31 MiB+ 205.23 KiB
/wp-admin/post-new.php0.768 s2.427 s+1.659 s5.27 MiB5.5 MiB+ 236.3 KiB
/wp-admin/upload.php0.685 s0.309 s-0.376 s3.03 MiB3.17 MiB+ 140.33 KiB
/wp-admin/options-writing.php0.145 s0.152 s+0.007 s3.02 MiB3.15 MiB+ 124.82 KiB
/wp-admin/media-new.php0.241 s0.204 s-0.037 s3.01 MiB3.15 MiB+ 142.06 KiB
/wp-admin/edit-tags.php?taxonomy=category0.163 s0.336 s+0.173 s3.04 MiB3.18 MiB+ 141.61 KiB
/wp-admin/post-new.php?post_type=page0.733 s5.262 s+4.529 s5.26 MiB10.42 MiB+ 5.17 MiB
/wp-admin/options-discussion.php0.322 s0.533 s+0.211 s3 MiB3.14 MiB+ 141.33 KiB
/wp-admin/edit-comments.php0.279 s0.222 s-0.057 s3.04 MiB3.18 MiB+ 139.55 KiB
/0.262 s0.210 s-0.052 s2.91 MiB3.04 MiB+ 128.59 KiB
Average 0.373 s0.917 s+0.545 s3.43 MiB4.04 MiB+ 621.13 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
PHP35.3%6,3473,05260
JavaScript33.7%6,061680105
Sass15.9%2,86412946
TypeScript10.1%1,80811844
Markdown3.4%61907
JSON0.9%15802
SVG0.6%10204
CSS0.1%2241
Total 17,981 3,983 269

PHP Code Analysis | More results »

Lines of code 5,942
Total complexity 1,032
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 110

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

[03-Aug-2021 21:44:33 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
[03-Aug-2021 21:44:33 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
[03-Aug-2021 21:44:33 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
[03-Aug-2021 21:44:37 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
[03-Aug-2021 21:44:37 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
[03-Aug-2021 21:44:37 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
[03-Aug-2021 21:44:44 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
[03-Aug-2021 21:44:44 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
[03-Aug-2021 21:44:44 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