1. Home
2. Gutenberg
3. 6.1.0

Gutenberg 6.1.0

Does Gutenberg work with WordPress 5.2.2 and PHP 7.2.16? A smoke test was performed on 2019-07-10 03:46:50 UTC.

Summary

Pages 4

Plugins ‹ Test site — WordPress

Gutenberg

Gutenberg → Widgets (beta)

Test site – Just another WordPress site

Benchmark

URL	Load time			Memory usage
	Inactive	Active	Change	Inactive	Active	Change
/wp-admin/index.php	0.372 s	0.300 s	-0.072 s	3.6 MiB	3.7 MiB	+ 106.67 KiB
/wp-admin/edit.php	0.255 s	0.474 s	+0.219 s	3.63 MiB	3.73 MiB	+ 106.23 KiB
/wp-admin/post-new.php	1.297 s	2.025 s	+0.728 s	5.27 MiB	5.62 MiB	+ 358.52 KiB
/wp-admin/upload.php	0.590 s	0.579 s	-0.011 s	3.46 MiB	3.56 MiB	+ 103.04 KiB
/wp-admin/options-writing.php	0.195 s	0.347 s	+0.152 s	3.55 MiB	3.56 MiB	+ 9.95 KiB
/wp-admin/media-new.php	0.284 s	0.346 s	+0.062 s	3.45 MiB	3.55 MiB	+ 103.52 KiB
/wp-admin/edit-tags.php?taxonomy=category	0.254 s	0.384 s	+0.130 s	3.48 MiB	3.65 MiB	+ 169.37 KiB
/wp-admin/post-new.php?post_type=page	1.343 s	1.913 s	+0.570 s	5.25 MiB	5.6 MiB	+ 359.73 KiB
/wp-admin/options-discussion.php	0.653 s	0.422 s	-0.231 s	3.45 MiB	3.55 MiB	+ 103.84 KiB
/wp-admin/edit-comments.php	0.264 s	0.401 s	+0.137 s	3.55 MiB	3.66 MiB	+ 103.06 KiB
/	0.441 s	0.377 s	-0.064 s	3.3 MiB	3.33 MiB	+ 22.68 KiB
Average	0.541 s	0.688 s	+0.147 s	3.82 MiB	3.96 MiB	+ 140.6 KiB

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.

Custom Post Types 1

ID	Name
wp_area	Block Area (Experimental)

PHP Error Log 6 lines

[10-Jul-2019 03:47:14 UTC] PHP Notice:  the_widget was called <strong>incorrectly</strong>. Widgets need to be registered using <code>register_widget()</code>, before they can be displayed. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 4.9.0.) in /wp-includes/functions.php on line 4773
[10-Jul-2019 03:47:14 UTC] PHP Notice:  the_widget was called <strong>incorrectly</strong>. Widgets need to be registered using <code>register_widget()</code>, before they can be displayed. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 4.9.0.) in /wp-includes/functions.php on line 4773
[10-Jul-2019 03:47:14 UTC] PHP Notice:  the_widget was called <strong>incorrectly</strong>. Widgets need to be registered using <code>register_widget()</code>, before they can be displayed. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 4.9.0.) in /wp-includes/functions.php on line 4773
[10-Jul-2019 03:47:14 UTC] PHP Notice:  the_widget was called <strong>incorrectly</strong>. Widgets need to be registered using <code>register_widget()</code>, before they can be displayed. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 4.9.0.) in /wp-includes/functions.php on line 4773
[10-Jul-2019 03:47:14 UTC] PHP Notice:  the_widget was called <strong>incorrectly</strong>. Widgets need to be registered using <code>register_widget()</code>, before they can be displayed. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 4.9.0.) in /wp-includes/functions.php on line 4773
[10-Jul-2019 03:47:14 UTC] PHP Notice:  the_widget was called <strong>incorrectly</strong>. Widgets need to be registered using <code>register_widget()</code>, before they can be displayed. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 4.9.0.) in /wp-includes/functions.php on line 4773

---