Does WordPress.com Editing Toolkit work with WordPress 5.8 and PHP 7.4.8? A smoke test was performed on .
9 | PHP notices |
No JavaScript exceptions | |
All test pages loaded successfully | |
No resource errors |
Memory usage: 621.13 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.
WordPress version | 5.8 |
---|---|
PHP version | 7.4.8 |
MySQL version | 8.0.21 |
PHP memory limit | 256M |
Last updated | |
---|---|
Active installs | 100,000+ |
WordPress.org page | https://wordpress.org/plugins/full-site-editing/ |
Badges |
Get badge code |
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=6426147880 |
Aspect | after-activation |
HTTP status | 200 |
Load time | 0.370 s |
Memory usage | 3.24 MiB |
JS errors | None |
Resource errors | None |
URL | / |
---|---|
Aspect | front-page |
HTTP status | 200 |
Load time | 0.251 s |
Memory usage | 3.03 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/widgets.php |
---|---|
Aspect | new-sidebar-widgets |
HTTP status | 200 |
Load time | 1.754 s |
Memory usage | 4.69 MiB |
JS errors | None |
Resource errors | None |
URL | Load time | Memory usage | ||||
---|---|---|---|---|---|---|
Inactive | Active | Change | Inactive | Active | Change | |
/wp-admin/index.php | 0.300 s | 0.246 s | -0.054 s | 3.08 MiB | 3.22 MiB | + 139.81 KiB |
/wp-admin/edit.php | 0.183 s | 0.200 s | +0.017 s | 3.11 MiB | 3.31 MiB | + 205.23 KiB |
/wp-admin/post-new.php | 0.836 s | 2.424 s | +1.588 s | 5.27 MiB | 5.5 MiB | + 236.3 KiB |
/wp-admin/upload.php | 0.559 s | 0.343 s | -0.216 s | 3.03 MiB | 3.17 MiB | + 140.33 KiB |
/wp-admin/options-writing.php | 0.320 s | 0.269 s | -0.051 s | 3.02 MiB | 3.15 MiB | + 124.82 KiB |
/wp-admin/media-new.php | 0.265 s | 0.231 s | -0.034 s | 3.01 MiB | 3.15 MiB | + 142.06 KiB |
/wp-admin/edit-tags.php?taxonomy=category | 0.211 s | 0.186 s | -0.025 s | 3.04 MiB | 3.18 MiB | + 141.61 KiB |
/wp-admin/post-new.php?post_type=page | 1.026 s | 5.584 s | +4.558 s | 5.26 MiB | 10.42 MiB | + 5.17 MiB |
/wp-admin/options-discussion.php | 0.290 s | 0.463 s | +0.173 s | 3 MiB | 3.14 MiB | + 141.33 KiB |
/wp-admin/edit-comments.php | 0.220 s | 0.231 s | +0.011 s | 3.04 MiB | 3.18 MiB | + 139.55 KiB |
/ | 0.338 s | 0.239 s | -0.099 s | 2.91 MiB | 3.04 MiB | + 128.59 KiB |
Average | 0.413 s | 0.947 s | +0.533 s | 3.43 MiB | 4.04 MiB | + 621.13 KiB |
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.2% | 6,350 | 3,053 | 60 | |
JavaScript | 33.8% | 6,083 | 681 | 105 | |
Sass | 16.0% | 2,878 | 129 | 46 | |
TypeScript | 10.0% | 1,808 | 118 | 44 | |
Markdown | 3.4% | 619 | 0 | 7 | |
JSON | 0.9% | 158 | 0 | 2 | |
SVG | 0.6% | 102 | 0 | 4 | |
CSS | 0.1% | 22 | 4 | 1 | |
Total | 18,020 | 3,985 | 269 |
Lines of code | 5,945 |
---|---|
Total complexity | 1,033 |
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 |
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.
wp_options
1ID | Name |
---|---|
wpcom-mailerlite | Mailerlite subscriber popup |
[05-Aug-2021 16:47:09 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
[05-Aug-2021 16:47:09 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
[05-Aug-2021 16:47:09 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
[05-Aug-2021 16:47:13 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
[05-Aug-2021 16:47:13 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
[05-Aug-2021 16:47:13 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
[05-Aug-2021 16:47:19 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
[05-Aug-2021 16:47:19 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
[05-Aug-2021 16:47:19 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