Does WordPress.com Editing Toolkit work with WordPress 5.7 and PHP 7.4.8? A smoke test was performed on .
4 | PHP notices |
No JavaScript exceptions | |
All test pages loaded successfully | |
No resource errors |
Memory usage: 595.28 KiB
The average PHP memory usage increased by this amount after activating by the plugin.
Page speed impact:
0.428 seconds
The average page load time increased by this amount after activating the plugin.
WordPress version | 5.7 |
---|---|
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=dfed896669 |
Aspect | after-activation |
HTTP status | 200 |
Load time | 0.242 s |
Memory usage | 2.92 MiB |
JS errors | None |
Resource errors | None |
URL | / |
---|---|
Aspect | front-page |
HTTP status | 200 |
Load time | 0.224 s |
Memory usage | 2.77 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/widgets.php |
---|---|
Aspect | new-sidebar-widgets |
HTTP status | 200 |
Load time | 0.738 s |
Memory usage | 2.97 MiB |
JS errors | None |
Resource errors | None |
URL | Load time | Memory usage | ||||
---|---|---|---|---|---|---|
Inactive | Active | Change | Inactive | Active | Change | |
/wp-admin/index.php | 0.260 s | 0.265 s | +0.005 s | 2.82 MiB | 2.96 MiB | + 145.11 KiB |
/wp-admin/edit.php | 0.183 s | 0.204 s | +0.021 s | 2.86 MiB | 2.99 MiB | + 131.88 KiB |
/wp-admin/post-new.php | 1.306 s | 2.273 s | +0.967 s | 5.02 MiB | 5.43 MiB | + 414.83 KiB |
/wp-admin/upload.php | 0.528 s | 0.268 s | -0.260 s | 2.7 MiB | 2.84 MiB | + 144.16 KiB |
/wp-admin/options-writing.php | 0.225 s | 0.142 s | -0.083 s | 2.71 MiB | 2.85 MiB | + 140.17 KiB |
/wp-admin/media-new.php | 0.214 s | 0.274 s | +0.060 s | 2.67 MiB | 2.81 MiB | + 144.7 KiB |
/wp-admin/edit-tags.php?taxonomy=category | 0.191 s | 0.207 s | +0.016 s | 2.77 MiB | 2.91 MiB | + 145.6 KiB |
/wp-admin/post-new.php?post_type=page | 0.627 s | 4.596 s | +3.969 s | 5.01 MiB | 9.76 MiB | + 4.75 MiB |
/wp-admin/options-discussion.php | 0.203 s | 0.290 s | +0.087 s | 2.67 MiB | 2.82 MiB | + 145.01 KiB |
/wp-admin/edit-comments.php | 0.257 s | 0.225 s | -0.032 s | 2.78 MiB | 2.92 MiB | + 144.48 KiB |
/ | 0.259 s | 0.220 s | -0.039 s | 2.65 MiB | 2.77 MiB | + 125.16 KiB |
Average | 0.387 s | 0.815 s | +0.428 s | 3.15 MiB | 3.73 MiB | + 595.28 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.0% | 5,878 | 2,788 | 57 | |
JavaScript | 32.6% | 5,641 | 1,055 | 105 | |
Sass | 17.3% | 2,989 | 130 | 48 | |
TypeScript | 10.8% | 1,876 | 316 | 45 | |
Markdown | 3.6% | 616 | 0 | 7 | |
JSON | 0.9% | 158 | 0 | 2 | |
SVG | 0.7% | 116 | 0 | 5 | |
CSS | 0.1% | 22 | 4 | 1 | |
Total | 17,296 | 4,293 | 270 |
Lines of code | 5,481 |
---|---|
Total complexity | 919 |
Median class complexity | 13.0 |
Median method complexity | 2.0 |
Most complex class | Newspack_Blocks |
Most complex function | newspack_blocks_render_block_carousel() |
Classes | 29 |
---|---|
Methods | 207 |
Functions | 85 |
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 |
[09-Apr-2021 13:11:11 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 5313
[09-Apr-2021 13:11:11 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 5313
[09-Apr-2021 13:11:15 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 5313
[09-Apr-2021 13:11:15 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 5313