WordPress.com Editing Toolkit 3.35321
Does WordPress.com Editing Toolkit work with WordPress 6.0 and PHP 7.4.8? A smoke test was performed on .
Summary
Errors
| 2 | PHP fatal errors |
| 24 | PHP notices |
| No JavaScript exceptions | |
| All test pages loaded successfully | |
| No resource errors |
Performance
Memory usage: 676.34 KiB
The average PHP memory usage increased by this amount after activating by the plugin.
Page speed impact:
0.823 seconds
The average page load time increased by this amount after activating the plugin.
Environment
| WordPress version | 6.0 |
|---|---|
| PHP version | 7.4.8 |
| MySQL version | 8.0.21 |
| PHP memory limit | 256M |
Plugin Info
| Last updated | |
|---|---|
| Active installs | 100,000+ |
| WordPress.org page | https://wordpress.org/plugins/full-site-editing/ |
| Badges |
|
Pages 3
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=35d448dbc6 |
| Aspect | after-activation |
| HTTP status | 200 |
| Load time | 0.312 s |
| Memory usage | 3.9 MiB |
| JS errors | None |
| Resource errors | None |
Test site – Just another WordPress site
| URL | / |
|---|---|
| Aspect | front-page |
| HTTP status | 200 |
| Load time | 0.203 s |
| Memory usage | 3.69 MiB |
| JS errors | None |
| Resource errors | None |
Widgets ‹ Test site — WordPress
| URL | /wp-admin/widgets.php |
|---|---|
| Aspect | new-sidebar-widgets |
| HTTP status | 200 |
| Load time | 2.105 s |
| Memory usage | 5.76 MiB |
| JS errors |
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.
|
| Resource errors | None |
Benchmark
| URL | Load time | Memory usage | ||||
|---|---|---|---|---|---|---|
| Inactive | Active | Change | Inactive | Active | Change | |
| /wp-admin/index.php | 0.363 s | 0.404 s | +0.041 s | 3.72 MiB | 3.86 MiB | + 144.99 KiB |
| /wp-admin/edit.php | 0.216 s | 0.273 s | +0.057 s | 3.75 MiB | 3.89 MiB | + 144.26 KiB |
| /wp-admin/post-new.php | 1.052 s | 2.747 s | +1.695 s | 5.53 MiB | 5.78 MiB | + 257.69 KiB |
| /wp-admin/upload.php | 0.439 s | 0.342 s | -0.097 s | 3.68 MiB | 3.82 MiB | + 143.89 KiB |
| /wp-admin/options-writing.php | 0.302 s | 0.166 s | -0.136 s | 3.61 MiB | 3.8 MiB | + 186.84 KiB |
| /wp-admin/media-new.php | 0.327 s | 0.210 s | -0.117 s | 3.66 MiB | 3.8 MiB | + 144.06 KiB |
| /wp-admin/edit-tags.php?taxonomy=category | 0.190 s | 0.199 s | +0.009 s | 3.68 MiB | 3.83 MiB | + 144.86 KiB |
| /wp-admin/post-new.php?post_type=page | 0.621 s | 8.034 s | +7.413 s | 5.53 MiB | 11.17 MiB | + 5.64 MiB |
| /wp-admin/options-discussion.php | 0.259 s | 0.499 s | +0.240 s | 3.59 MiB | 3.79 MiB | + 207.02 KiB |
| /wp-admin/edit-comments.php | 0.230 s | 0.239 s | +0.009 s | 3.69 MiB | 3.83 MiB | + 143.11 KiB |
| / | 0.298 s | 0.234 s | -0.064 s | 3.55 MiB | 3.69 MiB | + 148.32 KiB |
| Average | 0.391 s | 1.213 s | +0.823 s | 4 MiB | 4.66 MiB | + 676.34 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.
| Language | % | Lines of code | Comment lines | Files | |
|---|---|---|---|---|---|
| PHP | 36.7% | 6,460 | 3,155 | 66 | |
| JavaScript | 27.1% | 4,770 | 543 | 75 | |
| TypeScript | 15.3% | 2,695 | 124 | 54 | |
| Sass | 14.5% | 2,558 | 103 | 42 | |
| Markdown | 3.6% | 628 | 0 | 9 | |
| SVG | 1.0% | 174 | 0 | 7 | |
| JSON | 0.9% | 163 | 0 | 2 | |
| JSX | 0.7% | 127 | 16 | 2 | |
| CSS | 0.1% | 22 | 4 | 1 | |
| Total | 17,597 | 3,945 | 258 | ||
PHP Code Analysis | More results »
| Lines of code | 5,914 |
|---|---|
| Total complexity | 1,017 |
| Median class complexity | 8.0 |
| Median method complexity | 2.0 |
| Most complex class | Newspack_Blocks |
| Most complex function | newspack_blocks_render_block_carousel() |
| Classes | 35 |
|---|---|
| Methods | 219 |
| Functions | 119 |
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
- widget_wpcom-mailerlite
Sidebar Widgets 1
| ID | Name |
|---|---|
| wpcom-mailerlite | Mailerlite subscriber popup |
PHP Error Log 42 lines
[16-Jun-2022 21:44:44 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
[16-Jun-2022 21:44:44 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
[16-Jun-2022 21:44:44 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
[16-Jun-2022 21:44:44 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
[16-Jun-2022 21:44:44 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
[16-Jun-2022 21:44:44 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
[16-Jun-2022 21:44:44 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
[16-Jun-2022 21:44:44 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
[16-Jun-2022 21:44:45 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
[16-Jun-2022 21:44:48 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
[16-Jun-2022 21:44:48 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
[16-Jun-2022 21:44:48 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
[16-Jun-2022 21:44:48 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
[16-Jun-2022 21:44:48 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
[16-Jun-2022 21:44:48 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
[16-Jun-2022 21:44:48 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
[16-Jun-2022 21:44:48 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
[16-Jun-2022 21:44:54 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
[16-Jun-2022 21:44:58 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
[16-Jun-2022 21:44:58 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
[16-Jun-2022 21:44:58 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
[16-Jun-2022 21:44:58 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
[16-Jun-2022 21:44:58 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
[16-Jun-2022 21:44:58 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
[16-Jun-2022 21:44:58 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
[16-Jun-2022 21:44:58 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