Does WordPress.com Editing Toolkit work with WordPress 5.7.2 and PHP 7.4.8? A smoke test was performed on .
6 | PHP notices |
No JavaScript exceptions | |
All test pages loaded successfully | |
No resource errors |
Memory usage: 678.44 KiB
The average PHP memory usage increased by this amount after activating by the plugin.
Page speed impact:
0.614 seconds
The average page load time increased by this amount after activating the plugin.
WordPress version | 5.7.2 |
---|---|
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=8beed600fe |
Aspect | after-activation |
HTTP status | 200 |
Load time | 0.289 s |
Memory usage | 2.92 MiB |
JS errors | None |
Resource errors | None |
URL | / |
---|---|
Aspect | front-page |
HTTP status | 200 |
Load time | 0.242 s |
Memory usage | 2.78 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/widgets.php |
---|---|
Aspect | new-sidebar-widgets |
HTTP status | 200 |
Load time | 0.736 s |
Memory usage | 2.98 MiB |
JS errors | None |
Resource errors | None |
URL | Load time | Memory usage | ||||
---|---|---|---|---|---|---|
Inactive | Active | Change | Inactive | Active | Change | |
/wp-admin/index.php | 0.283 s | 0.256 s | -0.027 s | 2.82 MiB | 2.97 MiB | + 149.08 KiB |
/wp-admin/edit.php | 0.191 s | 0.212 s | +0.021 s | 2.86 MiB | 3 MiB | + 137.29 KiB |
/wp-admin/post-new.php | 0.963 s | 2.471 s | +1.508 s | 5.02 MiB | 5.43 MiB | + 420.3 KiB |
/wp-admin/upload.php | 0.488 s | 0.464 s | -0.024 s | 2.7 MiB | 2.9 MiB | + 213.23 KiB |
/wp-admin/options-writing.php | 0.265 s | 0.172 s | -0.093 s | 2.71 MiB | 2.89 MiB | + 182.09 KiB |
/wp-admin/media-new.php | 0.221 s | 0.194 s | -0.027 s | 2.67 MiB | 2.82 MiB | + 150.28 KiB |
/wp-admin/edit-tags.php?taxonomy=category | 0.211 s | 0.236 s | +0.025 s | 2.77 MiB | 2.92 MiB | + 152.13 KiB |
/wp-admin/post-new.php?post_type=page | 1.231 s | 6.508 s | +5.277 s | 5.01 MiB | 10.51 MiB | + 5.5 MiB |
/wp-admin/options-discussion.php | 0.322 s | 0.464 s | +0.142 s | 2.67 MiB | 2.82 MiB | + 150.59 KiB |
/wp-admin/edit-comments.php | 0.249 s | 0.236 s | -0.013 s | 2.78 MiB | 2.92 MiB | + 149.44 KiB |
/ | 0.277 s | 0.241 s | -0.036 s | 2.65 MiB | 2.78 MiB | + 128.22 KiB |
Average | 0.427 s | 1.041 s | +0.614 s | 3.15 MiB | 3.81 MiB | + 678.44 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.4% | 6,162 | 2,919 | 59 | |
JavaScript | 32.8% | 5,718 | 1,059 | 104 | |
Sass | 16.2% | 2,827 | 128 | 46 | |
TypeScript | 10.4% | 1,808 | 301 | 44 | |
Markdown | 3.6% | 619 | 0 | 7 | |
JSON | 0.9% | 158 | 0 | 2 | |
SVG | 0.6% | 102 | 0 | 4 | |
CSS | 0.1% | 22 | 4 | 1 | |
Total | 17,416 | 4,411 | 267 |
Lines of code | 5,765 |
---|---|
Total complexity | 971 |
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 | 220 |
Functions | 91 |
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 |
[19-Jul-2021 18:06:05 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 5313
[19-Jul-2021 18:06:05 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 5313
[19-Jul-2021 18:06:05 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 5313
[19-Jul-2021 18:06:10 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 5313
[19-Jul-2021 18:06:10 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 5313
[19-Jul-2021 18:06:10 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 5313