WordPress.com Editing Toolkit 4.11601
Does WordPress.com Editing Toolkit work with WordPress 6.4.2 and PHP 8.1.12? A smoke test was performed on .
Summary
Errors
| 3 | PHP fatal errors |
| 24 | PHP notices |
| No JavaScript exceptions | |
| 1 | Page failed to load
|
| No resource errors |
Performance
Memory usage: 150.83 KiB
The average PHP memory usage increased by this amount after activating by the plugin.
Page speed impact:
insignificant.
The plugin didn't make the site noticeably slower.
Environment
| WordPress version | 6.4.2 |
|---|---|
| PHP version | 8.1.12 |
| MySQL version | 10.6.10 |
| PHP memory limit | 512M |
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=381dd83e2b |
| Aspect | after-activation |
| HTTP status | 200 |
| Load time | 0.301 s |
| Memory usage | 3.55 MiB |
| JS errors | None |
| Resource errors | None |
Test site – Just another WordPress site
| URL | / |
|---|---|
| Aspect | front-page |
| HTTP status | 200 |
| Load time | 0.183 s |
| Memory usage | 3.47 MiB |
| JS errors | None |
| Resource errors | None |
WordPress › Error
| URL | /wp-admin/widgets.php |
|---|---|
| Aspect | new-sidebar-widgets |
| HTTP status | 500 |
| Load time | 0.094 s |
| Memory usage | N/A |
| JS errors | None |
| Resource errors | None |
Benchmark
| URL | Load time | Memory usage | ||||
|---|---|---|---|---|---|---|
| Inactive | Active | Change | Inactive | Active | Change | |
| /wp-admin/index.php | 0.351 s | 0.341 s | -0.010 s | 3.38 MiB | 3.54 MiB | + 166.41 KiB |
| /wp-admin/edit.php | 0.225 s | 0.231 s | +0.006 s | 3.41 MiB | 3.57 MiB | + 165.68 KiB |
| /wp-admin/upload.php | 0.740 s | 0.379 s | -0.361 s | 3.32 MiB | 3.47 MiB | + 149.83 KiB |
| /wp-admin/options-writing.php | 0.231 s | 0.211 s | -0.020 s | 3.32 MiB | 3.45 MiB | + 140.16 KiB |
| /wp-admin/media-new.php | 0.319 s | 0.483 s | +0.164 s | 3.29 MiB | 3.45 MiB | + 159.13 KiB |
| /wp-admin/edit-tags.php?taxonomy=category | 0.207 s | 0.198 s | -0.009 s | 3.31 MiB | 3.47 MiB | + 164.3 KiB |
| /wp-admin/options-discussion.php | 0.331 s | 0.230 s | -0.101 s | 3.3 MiB | 3.45 MiB | + 149.31 KiB |
| /wp-admin/edit-comments.php | 0.248 s | 0.232 s | -0.016 s | 3.33 MiB | 3.48 MiB | + 146.91 KiB |
| / | 0.295 s | 0.206 s | -0.089 s | 3.36 MiB | 3.47 MiB | + 115.73 KiB |
| Average | 0.327 s | 0.279 s | -0.048 s | 3.34 MiB | 3.48 MiB | + 150.83 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 | 35.4% | 7,495 | 3,574 | 76 | |
| JavaScript | 27.0% | 5,717 | 568 | 88 | |
| TypeScript | 16.2% | 3,428 | 178 | 44 | |
| Sass | 14.3% | 3,031 | 61 | 42 | |
| Markdown | 3.0% | 626 | 0 | 9 | |
| JSX | 1.6% | 335 | 28 | 5 | |
| SVG | 1.2% | 245 | 0 | 10 | |
| JSON | 1.0% | 216 | 0 | 3 | |
| XML | 0.1% | 26 | 0 | 1 | |
| CSS | 0.1% | 25 | 8 | 2 | |
| Total | 21,144 | 4,417 | 280 | ||
PHP Code Analysis | More results »
| Lines of code | 7,082 |
|---|---|
| Total complexity | 1,228 |
| Median class complexity | 7.0 |
| Median method complexity | 2.0 |
| Most complex class | Newspack_Blocks |
| Most complex function | newspack_blocks_render_block_carousel() |
| Classes | 49 |
|---|---|
| Methods | 303 |
| Functions | 108 |
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 54 lines
[29-Jan-2024 11:51:25 UTC] PHP Notice: Function WP_Scripts::localize was called incorrectly. The $l10n parameter must be an array. To pass arbitrary data to scripts, use the wp_add_inline_script() function instead. Please see <a>Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 6031
[29-Jan-2024 11:51:25 UTC] PHP Notice: Function WP_Scripts::localize was called incorrectly. The $l10n parameter must be an array. To pass arbitrary data to scripts, use the wp_add_inline_script() function instead. Please see <a>Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 6031
[29-Jan-2024 11:51:25 UTC] PHP Notice: Function WP_Scripts::localize was called incorrectly. The $l10n parameter must be an array. To pass arbitrary data to scripts, use the wp_add_inline_script() function instead. Please see <a>Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 6031
[29-Jan-2024 11:51:25 UTC] PHP Notice: Function WP_Scripts::localize was called incorrectly. The $l10n parameter must be an array. To pass arbitrary data to scripts, use the wp_add_inline_script() function instead. Please see <a>Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 6031
[29-Jan-2024 11:51:25 UTC] PHP Notice: Function WP_Scripts::localize was called incorrectly. The $l10n parameter must be an array. To pass arbitrary data to scripts, use the wp_add_inline_script() function instead. Please see <a>Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 6031
[29-Jan-2024 11:51:25 UTC] PHP Notice: Function WP_Scripts::localize was called incorrectly. The $l10n parameter must be an array. To pass arbitrary data to scripts, use the wp_add_inline_script() function instead. Please see <a>Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 6031
[29-Jan-2024 11:51:25 UTC] PHP Notice: Function WP_Scripts::localize was called incorrectly. The $l10n parameter must be an array. To pass arbitrary data to scripts, use the wp_add_inline_script() function instead. Please see <a>Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 6031
[29-Jan-2024 11:51:25 UTC] PHP Notice: Function WP_Scripts::localize was called incorrectly. The $l10n parameter must be an array. To pass arbitrary data to scripts, use the wp_add_inline_script() function instead. Please see <a>Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 6031
[29-Jan-2024 11:51:25 UTC] PHP Fatal error: Uncaught Error: Class "Jetpack_Options" not found in /wp-content/plugins/full-site-editing/wpcom-domain-upsell-callout/class-wpcom-domain-upsell-callout.php:84
Stack trace:
#0 /wp-content/plugins/full-site-editing/wpcom-domain-upsell-callout/class-wpcom-domain-upsell-callout.php(45): A8C\FSE\WPCOM_Domain_Upsell_Callout->should_not_show_callout()
#1 /wp-includes/class-wp-hook.php(324): A8C\FSE\WPCOM_Domain_Upsell_Callout->enqueue_script_and_style()
#2 /wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
#3 /wp-includes/plugin.php(517): WP_Hook->do_action()
#4 /wp-admin/edit-form-blocks.php(272): do_action()
#5 /wp-admin/post-new.php(72): require('...')
#6 {main}
thrown in /wp-content/plugins/full-site-editing/wpcom-domain-upsell-callout/class-wpcom-domain-upsell-callout.php on line 84
[29-Jan-2024 11:51:27 UTC] PHP Notice: Function WP_Scripts::localize was called incorrectly. The $l10n parameter must be an array. To pass arbitrary data to scripts, use the wp_add_inline_script() function instead. Please see <a>Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 6031
[29-Jan-2024 11:51:27 UTC] PHP Notice: Function WP_Scripts::localize was called incorrectly. The $l10n parameter must be an array. To pass arbitrary data to scripts, use the wp_add_inline_script() function instead. Please see <a>Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 6031
[29-Jan-2024 11:51:27 UTC] PHP Notice: Function WP_Scripts::localize was called incorrectly. The $l10n parameter must be an array. To pass arbitrary data to scripts, use the wp_add_inline_script() function instead. Please see <a>Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 6031
[29-Jan-2024 11:51:27 UTC] PHP Notice: Function WP_Scripts::localize was called incorrectly. The $l10n parameter must be an array. To pass arbitrary data to scripts, use the wp_add_inline_script() function instead. Please see <a>Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 6031
[29-Jan-2024 11:51:27 UTC] PHP Notice: Function WP_Scripts::localize was called incorrectly. The $l10n parameter must be an array. To pass arbitrary data to scripts, use the wp_add_inline_script() function instead. Please see <a>Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 6031
[29-Jan-2024 11:51:27 UTC] PHP Notice: Function WP_Scripts::localize was called incorrectly. The $l10n parameter must be an array. To pass arbitrary data to scripts, use the wp_add_inline_script() function instead. Please see <a>Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 6031
[29-Jan-2024 11:51:27 UTC] PHP Notice: Function WP_Scripts::localize was called incorrectly. The $l10n parameter must be an array. To pass arbitrary data to scripts, use the wp_add_inline_script() function instead. Please see <a>Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 6031
[29-Jan-2024 11:51:27 UTC] PHP Notice: Function WP_Scripts::localize was called incorrectly. The $l10n parameter must be an array. To pass arbitrary data to scripts, use the wp_add_inline_script() function instead. Please see <a>Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 6031
[29-Jan-2024 11:51:27 UTC] PHP Fatal error: Uncaught Error: Class "Jetpack_Options" not found in /wp-content/plugins/full-site-editing/wpcom-domain-upsell-callout/class-wpcom-domain-upsell-callout.php:84
Stack trace:
#0 /wp-content/plugins/full-site-editing/wpcom-domain-upsell-callout/class-wpcom-domain-upsell-callout.php(45): A8C\FSE\WPCOM_Domain_Upsell_Callout->should_not_show_callout()
#1 /wp-includes/class-wp-hook.php(324): A8C\FSE\WPCOM_Domain_Upsell_Callout->enqueue_script_and_style()
#2 /wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
#3 /wp-includes/plugin.php(517): WP_Hook->do_action()
#4 /wp-admin/edit-form-blocks.php(272): do_action()
#5 /wp-admin/post-new.php(72): require('...')
#6 {main}
thrown in /wp-content/plugins/full-site-editing/wpcom-domain-upsell-callout/class-wpcom-domain-upsell-callout.php on line 84
[29-Jan-2024 11:51:28 UTC] PHP Notice: Function WP_Scripts::localize was called incorrectly. The $l10n parameter must be an array. To pass arbitrary data to scripts, use the wp_add_inline_script() function instead. Please see <a>Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 6031
[29-Jan-2024 11:51:28 UTC] PHP Notice: Function WP_Scripts::localize was called incorrectly. The $l10n parameter must be an array. To pass arbitrary data to scripts, use the wp_add_inline_script() function instead. Please see <a>Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 6031
[29-Jan-2024 11:51:28 UTC] PHP Notice: Function WP_Scripts::localize was called incorrectly. The $l10n parameter must be an array. To pass arbitrary data to scripts, use the wp_add_inline_script() function instead. Please see <a>Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 6031
[29-Jan-2024 11:51:28 UTC] PHP Notice: Function WP_Scripts::localize was called incorrectly. The $l10n parameter must be an array. To pass arbitrary data to scripts, use the wp_add_inline_script() function instead. Please see <a>Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 6031
[29-Jan-2024 11:51:28 UTC] PHP Notice: Function WP_Scripts::localize was called incorrectly. The $l10n parameter must be an array. To pass arbitrary data to scripts, use the wp_add_inline_script() function instead. Please see <a>Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 6031
[29-Jan-2024 11:51:28 UTC] PHP Notice: Function WP_Scripts::localize was called incorrectly. The $l10n parameter must be an array. To pass arbitrary data to scripts, use the wp_add_inline_script() function instead. Please see <a>Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 6031
[29-Jan-2024 11:51:28 UTC] PHP Notice: Function WP_Scripts::localize was called incorrectly. The $l10n parameter must be an array. To pass arbitrary data to scripts, use the wp_add_inline_script() function instead. Please see <a>Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 6031
[29-Jan-2024 11:51:28 UTC] PHP Notice: Function WP_Scripts::localize was called incorrectly. The $l10n parameter must be an array. To pass arbitrary data to scripts, use the wp_add_inline_script() function instead. Please see <a>Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 6031
[29-Jan-2024 11:51:28 UTC] PHP Fatal error: Uncaught Error: Class "Jetpack_Options" not found in /wp-content/plugins/full-site-editing/wpcom-domain-upsell-callout/class-wpcom-domain-upsell-callout.php:84
Stack trace:
#0 /wp-content/plugins/full-site-editing/wpcom-domain-upsell-callout/class-wpcom-domain-upsell-callout.php(45): A8C\FSE\WPCOM_Domain_Upsell_Callout->should_not_show_callout()
#1 /wp-includes/class-wp-hook.php(324): A8C\FSE\WPCOM_Domain_Upsell_Callout->enqueue_script_and_style()
#2 /wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
#3 /wp-includes/plugin.php(517): WP_Hook->do_action()
#4 /wp-admin/widgets-form-blocks.php(65): do_action()
#5 /wp-admin/widgets.php(32): require('...')
#6 {main}
thrown in /wp-content/plugins/full-site-editing/wpcom-domain-upsell-callout/class-wpcom-domain-upsell-callout.php on line 84
See also: All tests for this plugin