1. Home
2. WordPress.com Editing Toolkit
3. 3.14741

WordPress.com Editing Toolkit 3.14741

Does WordPress.com Editing Toolkit work with WordPress 5.8.1 and PHP 7.4.8? A smoke test was performed on 2021-09-10 12:05:36 UTC.

Summary

Pages 3

Plugins ‹ Test site — WordPress

Test site – Just another WordPress site

Widgets ‹ Test site — WordPress

Benchmark

URL	Load time			Memory usage
	Inactive	Active	Change	Inactive	Active	Change
/wp-admin/index.php	0.488 s	0.297 s	-0.191 s	3.08 MiB	3.22 MiB	+ 143.71 KiB
/wp-admin/edit.php	0.238 s	0.221 s	-0.017 s	3.11 MiB	3.32 MiB	+ 209.13 KiB
/wp-admin/post-new.php	1.060 s	2.792 s	+1.732 s	5.27 MiB	5.5 MiB	+ 243.89 KiB
/wp-admin/upload.php	0.630 s	0.406 s	-0.224 s	3.03 MiB	3.17 MiB	+ 144.23 KiB
/wp-admin/options-writing.php	0.221 s	0.302 s	+0.081 s	3.02 MiB	3.15 MiB	+ 128.72 KiB
/wp-admin/media-new.php	0.318 s	0.302 s	-0.016 s	3.01 MiB	3.15 MiB	+ 145.96 KiB
/wp-admin/edit-tags.php?taxonomy=category	0.236 s	0.225 s	-0.011 s	3.04 MiB	3.18 MiB	+ 145.51 KiB
/wp-admin/post-new.php?post_type=page	0.740 s	6.669 s	+5.929 s	5.26 MiB	10.44 MiB	+ 5.19 MiB
/wp-admin/options-discussion.php	0.282 s	0.644 s	+0.362 s	3 MiB	3.14 MiB	+ 145.23 KiB
/wp-admin/edit-comments.php	0.282 s	0.261 s	-0.021 s	3.04 MiB	3.18 MiB	+ 143.45 KiB
/	0.352 s	0.249 s	-0.103 s	2.96 MiB	3.04 MiB	+ 84.83 KiB
Average	0.441 s	1.124 s	+0.684 s	3.44 MiB	4.05 MiB	+ 622.36 KiB

Code Statistics

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	35.3%	6,529	3,127	62
	JavaScript	33.9%	6,272	710	110
	Sass	15.7%	2,897	130	47
	TypeScript	10.2%	1,893	133	46
	Markdown	3.4%	623	0	8
	JSON	0.9%	163	0	2
	SVG	0.6%	102	0	4
	CSS	0.1%	22	4	1
Total			18,501	4,104	280

PHP Code Analysis | More results »

Additions

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.

Options wp_options 1

• widget_wpcom-mailerlite

Sidebar Widgets 1

ID	Name
wpcom-mailerlite	Mailerlite subscriber popup

PHP Error Log 12 lines

[10-Sep-2021 12:05: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
[10-Sep-2021 12:05: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
[10-Sep-2021 12:05: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
[10-Sep-2021 12:05: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
[10-Sep-2021 12:06: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
[10-Sep-2021 12:06: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
[10-Sep-2021 12:06: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
[10-Sep-2021 12:06: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
[10-Sep-2021 12:06:09 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-Sep-2021 12:06:09 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-Sep-2021 12:06:09 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-Sep-2021 12:06:09 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

---