Does WordPress.com Editing Toolkit work with WordPress 5.8.1 and PHP 7.4.8? A smoke test was performed on .
12 | PHP notices |
No JavaScript exceptions | |
All test pages loaded successfully | |
No resource errors |
Memory usage: 627.43 KiB
The average PHP memory usage increased by this amount after activating by the plugin.
Page speed impact:
0.476 seconds
The average page load time increased by this amount after activating the plugin.
WordPress version | 5.8.1 |
---|---|
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=3a4220f27a |
Aspect | after-activation |
HTTP status | 200 |
Load time | 0.400 s |
Memory usage | 3.25 MiB |
JS errors | None |
Resource errors | None |
URL | / |
---|---|
Aspect | front-page |
HTTP status | 200 |
Load time | 0.203 s |
Memory usage | 3.04 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/widgets.php |
---|---|
Aspect | new-sidebar-widgets |
HTTP status | 200 |
Load time | 2.692 s |
Memory usage | 4.7 MiB |
JS errors | None |
Resource errors | None |
URL | Load time | Memory usage | ||||
---|---|---|---|---|---|---|
Inactive | Active | Change | Inactive | Active | Change | |
/wp-admin/index.php | 0.303 s | 0.263 s | -0.040 s | 3.08 MiB | 3.22 MiB | + 144.48 KiB |
/wp-admin/edit.php | 0.179 s | 0.206 s | +0.027 s | 3.11 MiB | 3.32 MiB | + 209.89 KiB |
/wp-admin/post-new.php | 0.721 s | 2.352 s | +1.631 s | 5.27 MiB | 5.51 MiB | + 244.34 KiB |
/wp-admin/upload.php | 0.496 s | 0.301 s | -0.195 s | 3.03 MiB | 3.17 MiB | + 144.99 KiB |
/wp-admin/options-writing.php | 0.154 s | 0.146 s | -0.008 s | 3.02 MiB | 3.15 MiB | + 129.48 KiB |
/wp-admin/media-new.php | 0.415 s | 0.195 s | -0.220 s | 3.01 MiB | 3.15 MiB | + 146.73 KiB |
/wp-admin/edit-tags.php?taxonomy=category | 0.187 s | 0.185 s | -0.002 s | 3.04 MiB | 3.18 MiB | + 146.27 KiB |
/wp-admin/post-new.php?post_type=page | 1.180 s | 4.946 s | +3.766 s | 5.26 MiB | 10.44 MiB | + 5.19 MiB |
/wp-admin/options-discussion.php | 0.231 s | 0.390 s | +0.159 s | 3 MiB | 3.15 MiB | + 145.99 KiB |
/wp-admin/edit-comments.php | 0.201 s | 0.360 s | +0.159 s | 3.04 MiB | 3.18 MiB | + 144.21 KiB |
/ | 0.252 s | 0.206 s | -0.046 s | 2.91 MiB | 3.04 MiB | + 133.26 KiB |
Average | 0.393 s | 0.868 s | +0.476 s | 3.43 MiB | 4.05 MiB | + 627.43 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 | 34.9% | 6,531 | 3,135 | 62 | |
JavaScript | 33.8% | 6,323 | 711 | 110 | |
Sass | 16.0% | 2,996 | 130 | 47 | |
TypeScript | 10.3% | 1,923 | 139 | 47 | |
Markdown | 3.3% | 623 | 0 | 8 | |
JSON | 0.9% | 163 | 0 | 2 | |
SVG | 0.7% | 122 | 0 | 5 | |
CSS | 0.1% | 22 | 4 | 1 | |
Total | 18,703 | 4,119 | 282 |
Lines of code | 6,121 |
---|---|
Total complexity | 1,063 |
Median class complexity | 13.0 |
Median method complexity | 2.0 |
Most complex class | Newspack_Blocks |
Most complex function | newspack_blocks_render_block_carousel() |
Classes | 31 |
---|---|
Methods | 229 |
Functions | 115 |
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 |
[22-Oct-2021 14:49:00 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 5663
[22-Oct-2021 14:49:00 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 5663
[22-Oct-2021 14:49:00 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 5663
[22-Oct-2021 14:49:00 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 5663
[22-Oct-2021 14:49:04 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 5663
[22-Oct-2021 14:49:04 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 5663
[22-Oct-2021 14:49:04 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 5663
[22-Oct-2021 14:49:04 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 5663
[22-Oct-2021 14:49: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 5663
[22-Oct-2021 14:49: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 5663
[22-Oct-2021 14:49: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 5663
[22-Oct-2021 14:49: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 5663