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: 624.17 KiB
The average PHP memory usage increased by this amount after activating by the plugin.
Page speed impact:
0.470 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=4abcd93ecf |
Aspect | after-activation |
HTTP status | 200 |
Load time | 0.388 s |
Memory usage | 3.25 MiB |
JS errors | None |
Resource errors | None |
URL | / |
---|---|
Aspect | front-page |
HTTP status | 200 |
Load time | 0.240 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.951 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.296 s | 0.265 s | -0.031 s | 3.08 MiB | 3.22 MiB | + 144.48 KiB |
/wp-admin/edit.php | 0.155 s | 0.201 s | +0.046 s | 3.11 MiB | 3.32 MiB | + 209.89 KiB |
/wp-admin/post-new.php | 0.812 s | 2.234 s | +1.422 s | 5.27 MiB | 5.51 MiB | + 252.54 KiB |
/wp-admin/upload.php | 0.332 s | 0.298 s | -0.034 s | 3.03 MiB | 3.17 MiB | + 144.99 KiB |
/wp-admin/options-writing.php | 0.123 s | 0.155 s | +0.032 s | 3.02 MiB | 3.15 MiB | + 129.48 KiB |
/wp-admin/media-new.php | 0.360 s | 0.199 s | -0.161 s | 3.01 MiB | 3.15 MiB | + 146.73 KiB |
/wp-admin/edit-tags.php?taxonomy=category | 0.267 s | 0.275 s | +0.008 s | 3.04 MiB | 3.18 MiB | + 146.27 KiB |
/wp-admin/post-new.php?post_type=page | 0.767 s | 4.307 s | +3.540 s | 5.26 MiB | 10.45 MiB | + 5.19 MiB |
/wp-admin/options-discussion.php | 0.187 s | 0.499 s | +0.312 s | 3 MiB | 3.15 MiB | + 145.99 KiB |
/wp-admin/edit-comments.php | 0.175 s | 0.290 s | +0.115 s | 3.04 MiB | 3.18 MiB | + 144.21 KiB |
/ | 0.259 s | 0.181 s | -0.078 s | 2.96 MiB | 3.04 MiB | + 85.59 KiB |
Average | 0.339 s | 0.809 s | +0.470 s | 3.44 MiB | 4.05 MiB | + 624.17 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.3% | 6,578 | 3,162 | 63 | |
JavaScript | 33.8% | 6,483 | 717 | 110 | |
Sass | 15.9% | 3,053 | 132 | 49 | |
TypeScript | 11.2% | 2,146 | 160 | 51 | |
Markdown | 3.2% | 623 | 0 | 8 | |
JSON | 0.8% | 163 | 0 | 2 | |
SVG | 0.7% | 137 | 0 | 6 | |
CSS | 0.1% | 22 | 4 | 1 | |
Total | 19,205 | 4,175 | 290 |
Lines of code | 6,168 |
---|---|
Total complexity | 1,070 |
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 | 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 |
[16-Nov-2021 03:42:57 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
[16-Nov-2021 03:42:57 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
[16-Nov-2021 03:42:57 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
[16-Nov-2021 03:42:57 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
[16-Nov-2021 03:43:01 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
[16-Nov-2021 03:43:01 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
[16-Nov-2021 03:43:01 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
[16-Nov-2021 03:43:01 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
[16-Nov-2021 03:43:06 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
[16-Nov-2021 03:43:06 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
[16-Nov-2021 03:43:06 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
[16-Nov-2021 03:43:06 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