1. Home
2. Gutenberg
3. 6.2.0

Gutenberg 6.2.0

Does Gutenberg work with WordPress 5.2.2 and PHP 7.2.16? A smoke test was performed on 2019-07-31 09:13:55 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.371 s	0.320 s	-0.051 s	3.6 MiB	3.7 MiB	+ 108.91 KiB
/wp-admin/edit.php	0.258 s	0.439 s	+0.181 s	3.63 MiB	3.74 MiB	+ 108.47 KiB
/wp-admin/post-new.php	1.117 s	1.999 s	+0.882 s	5.27 MiB	5.63 MiB	+ 370.44 KiB
/wp-admin/upload.php	0.665 s	0.383 s	-0.282 s	3.46 MiB	3.57 MiB	+ 105.27 KiB
/wp-admin/options-writing.php	0.198 s	0.169 s	-0.029 s	3.55 MiB	3.56 MiB	+ 12.19 KiB
/wp-admin/media-new.php	0.275 s	0.407 s	+0.132 s	3.45 MiB	3.55 MiB	+ 105.76 KiB
/wp-admin/edit-tags.php?taxonomy=category	0.232 s	0.284 s	+0.052 s	3.48 MiB	3.65 MiB	+ 171.6 KiB
/wp-admin/post-new.php?post_type=page	1.019 s	2.081 s	+1.062 s	5.25 MiB	5.61 MiB	+ 371.65 KiB
/wp-admin/options-discussion.php	0.556 s	0.297 s	-0.259 s	3.45 MiB	3.55 MiB	+ 106.07 KiB
/wp-admin/edit-comments.php	0.230 s	0.469 s	+0.239 s	3.55 MiB	3.66 MiB	+ 105.3 KiB
/	0.446 s	0.429 s	-0.017 s	3.3 MiB	3.36 MiB	+ 61.7 KiB
Average	0.488 s	0.662 s	+0.174 s	3.82 MiB	3.96 MiB	+ 147.94 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

[31-Jul-2019 09:14:16 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
[31-Jul-2019 09:14:16 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
[31-Jul-2019 09:14:16 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
[31-Jul-2019 09:14:16 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
[31-Jul-2019 09:14:16 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
[31-Jul-2019 09:14:16 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

---