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: 620.37 KiB
The average PHP memory usage increased by this amount after activating by the plugin.
Page speed impact:
0.507 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=7bee25b21d |
Aspect | after-activation |
HTTP status | 200 |
Load time | 0.298 s |
Memory usage | 3.24 MiB |
JS errors | None |
Resource errors | None |
URL | / |
---|---|
Aspect | front-page |
HTTP status | 200 |
Load time | 0.199 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 | 2.443 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.285 s | 0.247 s | -0.038 s | 3.08 MiB | 3.22 MiB | + 139.05 KiB |
/wp-admin/edit.php | 0.178 s | 0.180 s | +0.002 s | 3.11 MiB | 3.31 MiB | + 204.46 KiB |
/wp-admin/post-new.php | 0.799 s | 2.303 s | +1.504 s | 5.27 MiB | 5.5 MiB | + 235.54 KiB |
/wp-admin/upload.php | 0.587 s | 0.312 s | -0.275 s | 3.03 MiB | 3.17 MiB | + 139.56 KiB |
/wp-admin/options-writing.php | 0.192 s | 0.149 s | -0.043 s | 3.02 MiB | 3.14 MiB | + 124.05 KiB |
/wp-admin/media-new.php | 0.246 s | 0.332 s | +0.086 s | 3.01 MiB | 3.14 MiB | + 141.3 KiB |
/wp-admin/edit-tags.php?taxonomy=category | 0.175 s | 0.212 s | +0.037 s | 3.04 MiB | 3.18 MiB | + 140.84 KiB |
/wp-admin/post-new.php?post_type=page | 0.976 s | 5.053 s | +4.077 s | 5.26 MiB | 10.42 MiB | + 5.17 MiB |
/wp-admin/options-discussion.php | 0.275 s | 0.386 s | +0.111 s | 3 MiB | 3.14 MiB | + 140.56 KiB |
/wp-admin/edit-comments.php | 0.196 s | 0.318 s | +0.122 s | 3.04 MiB | 3.18 MiB | + 138.78 KiB |
/ | 0.286 s | 0.278 s | -0.008 s | 2.91 MiB | 3.03 MiB | + 127.83 KiB |
Average | 0.381 s | 0.888 s | +0.507 s | 3.43 MiB | 4.04 MiB | + 620.37 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,353 | 3,056 | 60 | |
JavaScript | 33.7% | 6,083 | 681 | 105 | |
Sass | 16.0% | 2,885 | 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,030 | 3,988 | 269 |
Lines of code | 5,948 |
---|---|
Total complexity | 1,035 |
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 |
[19-Aug-2021 15:41:35 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
[19-Aug-2021 15:41:35 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
[19-Aug-2021 15:41:35 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
[19-Aug-2021 15:41:39 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
[19-Aug-2021 15:41:39 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
[19-Aug-2021 15:41:39 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
[19-Aug-2021 15:41:45 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
[19-Aug-2021 15:41:45 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
[19-Aug-2021 15:41:45 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