Does WordPress.com Editing Toolkit work with WordPress 5.8.2 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: 625.65 KiB
The average PHP memory usage increased by this amount after activating by the plugin.
Page speed impact:
0.486 seconds
The average page load time increased by this amount after activating the plugin.
WordPress version | 5.8.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=0184eef692 |
Aspect | after-activation |
HTTP status | 200 |
Load time | 0.430 s |
Memory usage | 3.25 MiB |
JS errors | None |
Resource errors | None |
URL | / |
---|---|
Aspect | front-page |
HTTP status | 200 |
Load time | 0.198 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 | 1.995 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.340 s | 0.293 s | -0.047 s | 3.08 MiB | 3.23 MiB | + 146.62 KiB |
/wp-admin/edit.php | 0.178 s | 0.215 s | +0.037 s | 3.11 MiB | 3.32 MiB | + 210.98 KiB |
/wp-admin/post-new.php | 0.927 s | 2.648 s | +1.721 s | 5.27 MiB | 5.52 MiB | + 255.41 KiB |
/wp-admin/upload.php | 0.366 s | 0.310 s | -0.056 s | 3.03 MiB | 3.17 MiB | + 146.09 KiB |
/wp-admin/options-writing.php | 0.279 s | 0.158 s | -0.121 s | 3.02 MiB | 3.15 MiB | + 130.58 KiB |
/wp-admin/media-new.php | 0.415 s | 0.223 s | -0.192 s | 3.01 MiB | 3.15 MiB | + 147.82 KiB |
/wp-admin/edit-tags.php?taxonomy=category | 0.195 s | 0.311 s | +0.116 s | 3.04 MiB | 3.18 MiB | + 147.37 KiB |
/wp-admin/post-new.php?post_type=page | 1.379 s | 5.001 s | +3.622 s | 5.26 MiB | 10.45 MiB | + 5.19 MiB |
/wp-admin/options-discussion.php | 0.221 s | 0.497 s | +0.276 s | 3 MiB | 3.15 MiB | + 147.14 KiB |
/wp-admin/edit-comments.php | 0.211 s | 0.261 s | +0.050 s | 3.04 MiB | 3.18 MiB | + 145.36 KiB |
/ | 0.252 s | 0.197 s | -0.055 s | 2.96 MiB | 3.04 MiB | + 86.51 KiB |
Average | 0.433 s | 0.919 s | +0.486 s | 3.44 MiB | 4.05 MiB | + 625.65 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.7% | 6,618 | 3,183 | 63 | |
JavaScript | 33.6% | 6,410 | 709 | 111 | |
Sass | 15.9% | 3,033 | 131 | 49 | |
TypeScript | 10.6% | 2,029 | 130 | 52 | |
Markdown | 3.3% | 623 | 0 | 8 | |
JSON | 0.9% | 163 | 0 | 2 | |
SVG | 0.7% | 137 | 0 | 6 | |
CSS | 0.1% | 22 | 4 | 1 | |
JSX | 0.1% | 20 | 0 | 1 | |
Total | 19,055 | 4,157 | 293 |
Lines of code | 6,208 |
---|---|
Total complexity | 1,080 |
Median class complexity | 12.5 |
Median method complexity | 2.0 |
Most complex class | Newspack_Blocks |
Most complex function | newspack_blocks_render_block_carousel() |
Classes | 32 |
---|---|
Methods | 233 |
Functions | 118 |
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 |
[10-Dec-2021 16:02:22 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
[10-Dec-2021 16:02:22 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
[10-Dec-2021 16:02:22 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
[10-Dec-2021 16:02:22 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
[10-Dec-2021 16:02:26 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
[10-Dec-2021 16:02:26 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
[10-Dec-2021 16:02:26 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
[10-Dec-2021 16:02:26 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
[10-Dec-2021 16:02:32 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
[10-Dec-2021 16:02:32 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
[10-Dec-2021 16:02:32 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
[10-Dec-2021 16:02:32 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