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

WordPress.com Editing Toolkit 3.24580

Does WordPress.com Editing Toolkit work with WordPress 5.8.3 and PHP 7.4.8? A smoke test was performed on 2022-01-14 08:06:42 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.304 s	0.256 s	-0.048 s	3.08 MiB	3.22 MiB	+ 145.43 KiB
/wp-admin/edit.php	0.178 s	0.180 s	+0.002 s	3.11 MiB	3.32 MiB	+ 209.48 KiB
/wp-admin/post-new.php	0.740 s	2.549 s	+1.809 s	5.27 MiB	5.52 MiB	+ 254.7 KiB
/wp-admin/upload.php	0.402 s	0.310 s	-0.092 s	3.03 MiB	3.17 MiB	+ 144.53 KiB
/wp-admin/options-writing.php	0.155 s	0.138 s	-0.017 s	3.02 MiB	3.15 MiB	+ 127.15 KiB
/wp-admin/media-new.php	0.411 s	0.219 s	-0.192 s	3.01 MiB	3.15 MiB	+ 144.7 KiB
/wp-admin/edit-tags.php?taxonomy=category	0.173 s	0.181 s	+0.008 s	3.04 MiB	3.18 MiB	+ 145.5 KiB
/wp-admin/post-new.php?post_type=page	0.932 s	4.958 s	+4.026 s	5.26 MiB	10.45 MiB	+ 5.19 MiB
/wp-admin/options-discussion.php	0.244 s	0.392 s	+0.148 s	3 MiB	3.14 MiB	+ 143.66 KiB
/wp-admin/edit-comments.php	0.206 s	0.219 s	+0.013 s	3.04 MiB	3.18 MiB	+ 143.75 KiB
/	0.319 s	0.209 s	-0.110 s	2.96 MiB	3.04 MiB	+ 86.18 KiB
Average	0.369 s	0.874 s	+0.504 s	3.44 MiB	4.05 MiB	+ 623.86 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.8%	6,707	3,355	65
	JavaScript	33.9%	6,544	729	111
	Sass	15.8%	3,044	133	49
	TypeScript	10.5%	2,029	130	52
	Markdown	3.2%	624	0	8
	JSON	0.8%	163	0	2
	SVG	0.7%	137	0	6
	CSS	0.1%	22	4	1
	JSX	0.1%	20	0	1
Total			19,290	4,351	295

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

[14-Jan-2022 08:06: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
[14-Jan-2022 08:06: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
[14-Jan-2022 08:06: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
[14-Jan-2022 08:06: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
[14-Jan-2022 08:07:02 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
[14-Jan-2022 08:07:02 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
[14-Jan-2022 08:07:02 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
[14-Jan-2022 08:07:02 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
[14-Jan-2022 08:07:08 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
[14-Jan-2022 08:07:08 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
[14-Jan-2022 08:07:08 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
[14-Jan-2022 08:07:08 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

---