WordPress.com Editing Toolkit 3.37573

Does WordPress.com Editing Toolkit work with WordPress 6.0.1 and PHP 7.4.8? A smoke test was performed on .

Summary

Errors
2PHP fatal errors
27PHP notices
1JavaScript exceptions
All test pages loaded successfully
No resource errors
Performance

Memory usage: 686.96 KiB
The average PHP memory usage increased by this amount after activating by the plugin.

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

Environment
WordPress version6.0.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=0f57611081
Aspect after-activation
HTTP status 200
Load time 0.293 s
Memory usage 3.91 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.207 s
Memory usage 3.7 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 2.889 s
Memory usage 5.8 MiB
JS errors
[
    {
        "message": "ReferenceError: No configuration was found: please see packages/calypso-config/README.md for more information\n    at Object.899 (/wp-content/plugins/full-site-editing/common/dist/data-stores.min.js?ver=75d7c5e342952f277280:7:50340)\n    at r (/wp-content/plugins/full-site-editing/common/dist/data-stores.min.js?ver=75d7c5e342952f277280:23:104248)\n    at Object.8459 (/wp-content/plugins/full-site-editing/common/dist/data-stores.min.js?ver=75d7c5e342952f277280:7:71974)\n    at r (/wp-content/plugins/full-site-editing/common/dist/data-stores.min.js?ver=75d7c5e342952f277280:23:104248)\n    at Object.2369 (/wp-content/plugins/full-site-editing/common/dist/data-stores.min.js?ver=75d7c5e342952f277280:7:78446)\n    at r (/wp-content/plugins/full-site-editing/common/dist/data-stores.min.js?ver=75d7c5e342952f277280:23:104248)\n    at Object.561 (/wp-content/plugins/full-site-editing/common/dist/data-stores.min.js?ver=75d7c5e342952f277280:7:49554)\n    at r (/wp-content/plugins/full-site-editing/common/dist/data-stores.min.js?ver=75d7c5e342952f277280:23:104248)\n    at /wp-content/plugins/full-site-editing/common/dist/data-stores.min.js?ver=75d7c5e342952f277280:23:104792\n    at /wp-content/plugins/full-site-editing/common/dist/data-stores.min.js?ver=75d7c5e342952f277280:23:104815",
        "trace": null,
        "code": null
    }
]
External errors: The following JavaScript errors were probably triggered by WordPress itself, or by compatibility issues in the test runner. They are not related to the plugin.
[
    {
        "message": "TypeError: Cannot read properties of null (reading 'offsetHeight')\n    at t (/wp-includes/js/dist/widgets.min.js?ver=80e98954519d1dad7a91a2248dbc2cc9:7:10419)\n    at IntersectionObserver.n.threshold (/wp-includes/js/dist/widgets.min.js?ver=80e98954519d1dad7a91a2248dbc2cc9:7:10591)",
        "trace": null,
        "code": null
    }
]
Resource errors None

Benchmark

URL Load time Memory usage
Inactive Active Change Inactive Active Change
/wp-admin/index.php0.363 s0.386 s+0.023 s3.72 MiB3.87 MiB+ 148.6 KiB
/wp-admin/edit.php0.205 s0.291 s+0.086 s3.75 MiB3.9 MiB+ 147.16 KiB
/wp-admin/post-new.php1.036 s3.784 s+2.748 s5.54 MiB5.82 MiB+ 283.82 KiB
/wp-admin/upload.php0.471 s0.369 s-0.102 s3.68 MiB3.83 MiB+ 147.5 KiB
/wp-admin/options-writing.php0.150 s0.168 s+0.018 s3.62 MiB3.8 MiB+ 190.05 KiB
/wp-admin/media-new.php0.560 s0.239 s-0.321 s3.66 MiB3.81 MiB+ 147.67 KiB
/wp-admin/edit-tags.php?taxonomy=category0.198 s0.228 s+0.030 s3.69 MiB3.83 MiB+ 148.47 KiB
/wp-admin/post-new.php?post_type=page1.134 s8.525 s+7.391 s5.54 MiB11.29 MiB+ 5.75 MiB
/wp-admin/options-discussion.php0.225 s0.445 s+0.220 s3.6 MiB3.8 MiB+ 210.63 KiB
/wp-admin/edit-comments.php0.226 s0.235 s+0.009 s3.69 MiB3.84 MiB+ 146.72 KiB
/0.290 s0.232 s-0.058 s3.6 MiB3.7 MiB+ 97.47 KiB
Average 0.442 s1.355 s+0.913 s4.01 MiB4.68 MiB+ 686.96 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
TypeScript
Sass
Language % Lines of code Comment lines Files
PHP38.4%7,0073,45873
JavaScript26.2%4,78954375
TypeScript14.9%2,72812854
Sass14.1%2,57110443
Markdown3.4%62809
SVG1.0%17407
JSX0.9%166163
JSON0.9%16302
CSS0.1%2582
Total 18,251 4,257 268

PHP Code Analysis | More results »

Lines of code 6,461
Total complexity 1,116
Median class complexity 8.0
Median method complexity 2.0
Most complex class Newspack_Blocks
Most complex function newspack_blocks_render_block_carousel()
Classes 41
Methods 261
Functions 126

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 45 lines

[20-Jul-2022 11:46:18 UTC] PHP Notice:  Function 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 5831
[20-Jul-2022 11:46:18 UTC] PHP Notice:  Function 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 5831
[20-Jul-2022 11:46:18 UTC] PHP Notice:  Function 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 5831
[20-Jul-2022 11:46:18 UTC] PHP Notice:  Function 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 5831
[20-Jul-2022 11:46:18 UTC] PHP Notice:  Function 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 5831
[20-Jul-2022 11:46:18 UTC] PHP Notice:  Function 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 5831
[20-Jul-2022 11:46:18 UTC] PHP Notice:  Function 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 5831
[20-Jul-2022 11:46:18 UTC] PHP Notice:  Function 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 5831
[20-Jul-2022 11:46:18 UTC] PHP Notice:  Function 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 5831
[20-Jul-2022 11:46:21 UTC] PHP Fatal error:  Uncaught Error: Call to undefined function WPForTeams\is_wpforteams_site() in /wp-content/plugins/full-site-editing/wpcom-block-editor-nux/class-wp-rest-wpcom-block-editor-nux-status-controller.php:86
Stack trace:
#0 /wp-includes/rest-api/class-wp-rest-server.php(1143): A8C\FSE\WP_REST_WPCOM_Block_Editor_NUX_Status_Controller->get_nux_status()
#1 /wp-includes/rest-api/class-wp-rest-server.php(990): WP_REST_Server->respond_to_request()
#2 /wp-includes/rest-api/class-wp-rest-server.php(414): WP_REST_Server->dispatch()
#3 /wp-includes/rest-api.php(394): WP_REST_Server->serve_request()
#4 /wp-includes/class-wp-hook.php(307): rest_api_loaded()
#5 /wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters()
#6 /wp-includes/plugin.php(524): WP_Hook in /wp-content/plugins/full-site-editing/wpcom-block-editor-nux/class-wp-rest-wpcom-block-editor-nux-status-controller.php on line 86
[20-Jul-2022 11:46:23 UTC] PHP Notice:  Function 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 5831
[20-Jul-2022 11:46:23 UTC] PHP Notice:  Function 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 5831
[20-Jul-2022 11:46:23 UTC] PHP Notice:  Function 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 5831
[20-Jul-2022 11:46:23 UTC] PHP Notice:  Function 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 5831
[20-Jul-2022 11:46:23 UTC] PHP Notice:  Function 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 5831
[20-Jul-2022 11:46:23 UTC] PHP Notice:  Function 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 5831
[20-Jul-2022 11:46:23 UTC] PHP Notice:  Function 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 5831
[20-Jul-2022 11:46:23 UTC] PHP Notice:  Function 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 5831
[20-Jul-2022 11:46:23 UTC] PHP Notice:  Function 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 5831
[20-Jul-2022 11:46:30 UTC] PHP Fatal error:  Uncaught Error: Call to undefined function WPForTeams\is_wpforteams_site() in /wp-content/plugins/full-site-editing/wpcom-block-editor-nux/class-wp-rest-wpcom-block-editor-nux-status-controller.php:86
Stack trace:
#0 /wp-includes/rest-api/class-wp-rest-server.php(1143): A8C\FSE\WP_REST_WPCOM_Block_Editor_NUX_Status_Controller->get_nux_status()
#1 /wp-includes/rest-api/class-wp-rest-server.php(990): WP_REST_Server->respond_to_request()
#2 /wp-includes/rest-api/class-wp-rest-server.php(414): WP_REST_Server->dispatch()
#3 /wp-includes/rest-api.php(394): WP_REST_Server->serve_request()
#4 /wp-includes/class-wp-hook.php(307): rest_api_loaded()
#5 /wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters()
#6 /wp-includes/plugin.php(524): WP_Hook in /wp-content/plugins/full-site-editing/wpcom-block-editor-nux/class-wp-rest-wpcom-block-editor-nux-status-controller.php on line 86
[20-Jul-2022 11:46:34 UTC] PHP Notice:  Function 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 5831
[20-Jul-2022 11:46:34 UTC] PHP Notice:  Function 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 5831
[20-Jul-2022 11:46:34 UTC] PHP Notice:  Function 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 5831
[20-Jul-2022 11:46:34 UTC] PHP Notice:  Function 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 5831
[20-Jul-2022 11:46:34 UTC] PHP Notice:  Function 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 5831
[20-Jul-2022 11:46:34 UTC] PHP Notice:  Function 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 5831
[20-Jul-2022 11:46:34 UTC] PHP Notice:  Function 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 5831
[20-Jul-2022 11:46:34 UTC] PHP Notice:  Function 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 5831
[20-Jul-2022 11:46:34 UTC] PHP Notice:  Function 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 5831
See also: All tests for this plugin