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

WordPress.com Editing Toolkit 3.19643

Does WordPress.com Editing Toolkit work with WordPress 5.8.2 and PHP 7.4.8? A smoke test was performed on 2021-11-17 03:28:33 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.333 s	0.299 s	-0.034 s	3.08 MiB	3.22 MiB	+ 144.48 KiB
/wp-admin/edit.php	0.213 s	0.208 s	-0.005 s	3.11 MiB	3.32 MiB	+ 209.89 KiB
/wp-admin/post-new.php	1.191 s	2.417 s	+1.226 s	5.27 MiB	5.51 MiB	+ 252.54 KiB
/wp-admin/upload.php	0.371 s	0.308 s	-0.063 s	3.03 MiB	3.17 MiB	+ 144.99 KiB
/wp-admin/options-writing.php	0.242 s	0.148 s	-0.094 s	3.02 MiB	3.15 MiB	+ 129.48 KiB
/wp-admin/media-new.php	0.288 s	0.217 s	-0.071 s	3.01 MiB	3.15 MiB	+ 146.73 KiB
/wp-admin/edit-tags.php?taxonomy=category	0.166 s	0.195 s	+0.029 s	3.04 MiB	3.18 MiB	+ 146.27 KiB
/wp-admin/post-new.php?post_type=page	0.685 s	4.807 s	+4.122 s	5.26 MiB	10.45 MiB	+ 5.19 MiB
/wp-admin/options-discussion.php	0.218 s	0.378 s	+0.160 s	3 MiB	3.15 MiB	+ 145.99 KiB
/wp-admin/edit-comments.php	0.197 s	0.215 s	+0.018 s	3.04 MiB	3.18 MiB	+ 144.21 KiB
/	0.268 s	0.202 s	-0.066 s	2.96 MiB	3.04 MiB	+ 85.59 KiB
Average	0.379 s	0.854 s	+0.475 s	3.44 MiB	4.05 MiB	+ 624.17 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	34.2%	6,578	3,162	63
	JavaScript	33.7%	6,485	717	110
	Sass	15.9%	3,053	132	49
	TypeScript	11.2%	2,158	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,219	4,175	290

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

[17-Nov-2021 03:28:48 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
[17-Nov-2021 03:28:48 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
[17-Nov-2021 03:28:48 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
[17-Nov-2021 03:28:48 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
[17-Nov-2021 03:28:52 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
[17-Nov-2021 03:28:52 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
[17-Nov-2021 03:28:52 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
[17-Nov-2021 03:28:52 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
[17-Nov-2021 03:28:58 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
[17-Nov-2021 03:28:58 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
[17-Nov-2021 03:28:58 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
[17-Nov-2021 03:28:58 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

---