Fatal Error After Update to 5.0

[miqrogroove]

I received the "WordPress 5.0 is imminent" e-mail today. The only way I could figure out to install 5.0 was via SVN checkout on the branch path.

I got as far as the Dashboard, where it asked me to install and activate Gutenburg. This operation failed and threw a fatal error on the Dashboard:

Fatal error: Cannot declare class WP_REST_Autosaves_Controller, because the name is already in use in /wp-content/plugins/gutenberg/lib/class-wp-rest-autosaves-controller.php on line 387

[miqrogroove]

Version says 5.0-alpha-43775

[earnjam]

The Gutenberg plugin & the 5.0 branch are not currently compatible as we work through the merge process.

This will be resolved when the 5.0 beta is released soon.

[miqrogroove]

My thoughts here: 5.0 does not appear to be ready for testing. I am putting the "WordPress 5.0 is imminent" message straight in the Trash, and I imagine others might do the same.

Can we do anything to clarify the branch timeline and expectations for plugin developers?

[SergeyBiryukov]

Related: #45123, #45073.

Looks like this is already addressed in [43765].

[miqrogroove]

I got the error after installing r43775. So this was not fixed yet.

[pento]

[43765] only disables the Gutenberg plugin on upgrade, it doesn't re-disable the Gutenberg plugin when someone enables it.

WordPress 5.0 and Gutenberg 4.1+ will be able to work together, Gutenberg 4.0 (and older) won't function with WordPress 5.0.

WordPress 5.0 beta 1 won't require the Gutenberg plugin to be able to test, I expect it will be available early next week. Unfortunately, the email went out a little early.

If you want to start testing now, you can test the WordPress 5.0 nightly with Gutenberg master, they should be working correctly.

​http://github.com/wordpress/gutenberg