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: 627.09 KiB
The average PHP memory usage increased by this amount after activating by the plugin.
Page speed impact:
0.485 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=02930d8137 |
Aspect | after-activation |
HTTP status | 200 |
Load time | 0.410 s |
Memory usage | 3.25 MiB |
JS errors | None |
Resource errors | None |
URL | / |
---|---|
Aspect | front-page |
HTTP status | 200 |
Load time | 0.264 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.043 s |
Memory usage | 4.71 MiB |
JS errors | None |
Resource errors | None |
URL | Load time | Memory usage | ||||
---|---|---|---|---|---|---|
Inactive | Active | Change | Inactive | Active | Change | |
/wp-admin/index.php | 0.294 s | 0.261 s | -0.033 s | 3.08 MiB | 3.23 MiB | + 147.98 KiB |
/wp-admin/edit.php | 0.174 s | 0.207 s | +0.033 s | 3.11 MiB | 3.32 MiB | + 212.34 KiB |
/wp-admin/post-new.php | 0.878 s | 2.584 s | +1.706 s | 5.27 MiB | 5.52 MiB | + 257.61 KiB |
/wp-admin/upload.php | 0.395 s | 0.331 s | -0.064 s | 3.03 MiB | 3.17 MiB | + 147.45 KiB |
/wp-admin/options-writing.php | 0.294 s | 0.159 s | -0.135 s | 3.02 MiB | 3.15 MiB | + 131.94 KiB |
/wp-admin/media-new.php | 0.420 s | 0.201 s | -0.219 s | 3.01 MiB | 3.15 MiB | + 149.18 KiB |
/wp-admin/edit-tags.php?taxonomy=category | 0.186 s | 0.184 s | -0.002 s | 3.04 MiB | 3.18 MiB | + 148.73 KiB |
/wp-admin/post-new.php?post_type=page | 1.305 s | 5.133 s | +3.828 s | 5.26 MiB | 10.45 MiB | + 5.19 MiB |
/wp-admin/options-discussion.php | 0.231 s | 0.375 s | +0.144 s | 3 MiB | 3.15 MiB | + 148.45 KiB |
/wp-admin/edit-comments.php | 0.200 s | 0.329 s | +0.129 s | 3.04 MiB | 3.19 MiB | + 146.66 KiB |
/ | 0.267 s | 0.219 s | -0.048 s | 2.96 MiB | 3.04 MiB | + 88.05 KiB |
Average | 0.422 s | 0.908 s | +0.485 s | 3.44 MiB | 4.05 MiB | + 627.09 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,637 | 3,194 | 64 | |
JavaScript | 33.8% | 6,469 | 725 | 111 | |
Sass | 15.9% | 3,038 | 134 | 49 | |
TypeScript | 10.6% | 2,029 | 130 | 52 | |
Markdown | 3.3% | 624 | 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,139 | 4,187 | 294 |
Lines of code | 6,227 |
---|---|
Total complexity | 1,083 |
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 | 120 |
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-Dec-2021 22:19: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 5663
[16-Dec-2021 22:19: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 5663
[16-Dec-2021 22:19: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 5663
[16-Dec-2021 22:19: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 5663
[16-Dec-2021 22:19:43 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-Dec-2021 22:19:43 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-Dec-2021 22:19:43 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-Dec-2021 22:19:43 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-Dec-2021 22:19:49 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-Dec-2021 22:19:49 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-Dec-2021 22:19:49 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-Dec-2021 22:19:49 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