Breaks every site

It’s my understanding, with WordPress 5.0 Guttenberg will be no different than WordPress 4.9.8 meaning you can decide which to use, Classic Editor or Gutenberg.

Unless this has changed, but according to Matt, 5.0 other than WordPress core bug fixes, will be no different than 4.9.8 his quotes
“If we keep the 5.0 release to strictly 4.9.8 + Gutenberg, we will have a release that is both major and a non-event in terms of new code,” Mullenweg said. “It’s all battle-tested. In some ways, 5.0 is already de facto out in the wild, with some forward-looking hosts already installing and activating Gutenberg for new installs.”

So, unless something has changed, I believe you should be good with 5.0 install. Someone that has used the 5.0 Beta Version should confirm.

So 5.0 will ship with Gutenberg as a plug-in that can be deactivated (or even better, a plug-in that isn’t active by default)? If that’s the case, then I’m a little less concerned, though I’m most concerned about TinyMCE being phased out of core and relegated to a community-supported plug-in – basically that the classic editor and Gutenberg will switch places.

It’s not that I mind terribly if the classic editor is a plug-in or core, but that moving forward decisions related to the editor will be made without any consideration for TinyMCE, and this will be a constant game of waiting for the classic editor plug-in to be updated to conform to the latest WP version, which puts way too much important functionality outside the purview of the core build. That makes me nervous as hell.

Unfortunately, @studio1337, as far as I can tell, 5.0 ships with Gutenberg installed into core. That has been the plan all along; no amount of complaining seems to have any effect on this. ??

I have been running a beta version of WP that gets the nightly beta builds, and for a while Gutenberg was active on it, but after one beta upgrade or other, it deactivated Gutenberg-the-plugin. So I would surmise that it seems to be firmly ensconced in core now, because if I turn on or off the Gutenberg plugin, I still get the Gutenberg editor. (That is, it seems to work with Gutenberg-the-plugin on or off, which is sort of interesting; I would think it should automatically turn off.)

Installing the Classic Editor plugin, which I think is a choice you get to make when a site upgrades to 5.0, restores my Custom Fields.

This test site is using WP version (5.0-beta3-43878), and version 4.4.0 of Gutenberg and 5.7.7 of Advanced Custom Fields Pro.

If you do not see your Custom Fields (either Advanced or “normal”):
You simply need to go up to the top right of the Gutenberg editor and click the 3 dots. (That used to be clearly labeled “Screen options” in the old editor.) Look at the bottom of that panel for the Options button, which is sort of separated from the other topics like View, Editor, and Tools, for some reason. Click that. Then look for Advanced Panels. Then find Custom Fields and click that. (This may reload your page, so if you have done any editing, save it first just in case.) With a little testing, it does seem to me that “normal” custom fields continue to show at the bottom below the Gutenberg editor. Easy enough!

Bear in mind, to make life interesting, Advanced Custom Fields will turn off the “normal” custom fields, unless you add some special code to your functions.php file to make it show both ACF and normal custom fields. I am not sure how Gutenberg will play into this.

Hi @bkjproductions – thank you very much for your reply. I was wondering where this setting might be. That wasn’t the most intuitive placement, but at least it’s accessible. That said, as you suggested, this would only make meta data fields available, but this strips away all of the ACF functionality that makes it useful (like flexible layouts, repeaters, etc.). It’s just the list of custom fields and a place to enter a value. All of the structure is gone.

If this was some esoteric plug-in with which we were experimenting on a site or two, I might be less stressed about it, but this is a widely used plug-in with TONS of power and support, and to say we rely on it as a development tool would be an understatement. Frankly, outside of the absolute most basic sites and extremely complex, fully custom-programmed sites (what I imagine to be the upper .1% and the lower 10% of all WP sites), I can’t imagine a developer not making use of this tool in his or her work.

I understand it’s up to plug-in developers to make their plug-ins work as expected with future releases of WordPress. It just seems like the infrastructure that allows ACF to function so robustly for developers is completely removed from sites once Gutenberg is turned on, and of course the one test we ran where nothing whatsoever loaded is going to be extremely problematic, as nothing whatsoever can be done with that site or any others that display the same result. I need to be able to add content meta to the tops, bottoms and sides of the main editor for proper edit-page workflow, and the mechanisms that power that metadata need to be intact. Gutenberg renders our sites functionally impotent across the board. We often program pages/sites to bypass the default editor entirely, telling clients to only use it for brief page summaries so text shows up in internal site searches. Forcing us to use it as the primary (or only) content vehicle is abominable.

Folks, these are reviews, not discussions. Good stuff, but please take it to a blog or Twizzler, or Fatebook.