clwill

Well, I think I’ll do that. I added “title” to the Supports clause of the CPT and it works. This is definitively a bug.

Yep, and the error happened when all of them were disabled as well.

OK, I’ve done all that (disabled plugins, etc.), added script-debug, and I still have the problem. Tested in Chrome, Firefox, and Safari. Here is the error

[Error] TypeError: null is not an object (evaluating 'ref.current.ownerDocument')
	(anonymous function) (editor.js:11734)
	commitHookEffectListMount (react-dom.js:19866)
	commitPassiveHookEffects (react-dom.js:19904)
	callCallback (react-dom.js:182)
	dispatchEvent
	invokeGuardedCallbackDev (react-dom.js:231)
	invokeGuardedCallback (react-dom.js:286)
	flushPassiveEffectsImpl (react-dom.js:22988)
	unstable_runWithPriority (react.js:2685)
	performSyncWorkOnRoot (react-dom.js:21872)
	performSyncWorkOnRoot
	(anonymous function) (react-dom.js:11224)
	unstable_runWithPriority (react.js:2685)
	flushSyncCallbackQueueImpl (react-dom.js:11219)
	flushSyncCallbackQueue (react-dom.js:11207)
	flushPendingDiscreteUpdates (react-dom.js:21982)
	flushDiscreteUpdates (react-dom.js:21962)
	flushDiscreteUpdatesIfNeeded (react-dom.js:826)
	dispatchDiscreteEvent (react-dom.js:4290)
	dispatchDiscreteEvent
[Error] The above error occurred in the <PostTitle> component:
    in PostTitle (created by VisualEditor)
    in div (created by VisualEditor)
    in div (created by WritingFlow)
    in WritingFlow (created by VisualEditor)
    in div (created by VisualEditor)
    in div (created by VisualEditor)
    in VisualEditor (created by Layout)
    in div (created by ForwardRef(InterfaceSkeleton))
    in div (created by ForwardRef(InterfaceSkeleton))
    in div (created by ForwardRef(InterfaceSkeleton))
    in div (created by ForwardRef(InterfaceSkeleton))
    in ForwardRef(InterfaceSkeleton) (created by Layout)
    in Layout (created by Editor)
    in ErrorBoundary (created by Editor)
    in BlockEditorProvider
    in Unknown (created by Context.Consumer)
    in WithRegistryProvider(BlockEditorProvider) (created by EditorProvider)
    in BlockContextProvider (created by EditorProvider)
    in EntityProvider (created by EditorProvider)
    in EntityProvider (created by EditorProvider)
    in EditorProvider
    in Unknown (created by Context.Consumer)
    in WithRegistryProvider(EditorProvider) (created by Editor)
    in DropZoneContextProvider (created by Editor)
    in slot_fill_provider_SlotFillProvider (created by SlotFillProvider)
    in SlotFillProvider (created by Editor)
    in StrictMode (created by Editor)
    in Editor

React will try to recreate this component tree from scratch using the error boundary you provided, ErrorBoundary.
	logCapturedError (react-dom.js:19662)
	logError (react-dom.js:19699)
	callback (react-dom.js:20879)
	callCallback (react-dom.js:12625)
	commitUpdateQueue (react-dom.js:12646)
	commitLifeCycles (react-dom.js:19993)
	commitLayoutEffects (react-dom.js:22938)
	callCallback (react-dom.js:182)
	dispatchEvent
	invokeGuardedCallbackDev (react-dom.js:231)
	invokeGuardedCallback (react-dom.js:286)
	commitRootImpl (react-dom.js:22676)
	commitRootImpl
	unstable_runWithPriority (react.js:2685)
	commitRoot (react-dom.js:22516)
	finishSyncRender (react-dom.js:21942)
	performSyncWorkOnRoot (react-dom.js:21928)
	performSyncWorkOnRoot
	(anonymous function) (react-dom.js:11224)
	unstable_runWithPriority (react.js:2685)
	flushSyncCallbackQueueImpl (react-dom.js:11219)
	flushSyncCallbackQueue (react-dom.js:11207)
	flushPendingDiscreteUpdates (react-dom.js:21982)
	flushDiscreteUpdates (react-dom.js:21962)
	flushDiscreteUpdatesIfNeeded (react-dom.js:826)
	dispatchDiscreteEvent (react-dom.js:4290)
	dispatchDiscreteEvent

I’d love a way to do this as well. For right now, I think I’m going to have to do it with a ACF Pro block. But it sure would be nice if the block editor would provide fields for these “grouping” elements to support a link.

I second @simonfishley and his response. I had this error, installing the php-mbstring package solved the problem. Thank you @simonfishley !

Yes, I did. Turns out I had two versions of PHP installed. One had CURL, one didn’t. The one that Nginx was referencing didn’t, but the command line one did. Removed the older version, pointed Nginx to the new version, and voila, everything works fine.

Is there some way, some place to report this? Or is this post sufficient?

I’d hate to see this happen to someone else. At the very least there should be some way to do a “reset Gutenberg to defaults” option, no?

I have it working again. With my theme.

What I did was change to 2019, cleared my cache, which got me into Gutenberg, which allowed me to go into options and turn OFF the “custom fields” option.

I then went back to my theme, again cleared my cache, and now Gutenberg works with my theme.

I have no idea what “custom fields” the option page is referring to, my theme doesn’t reference any “custom fields” that I know of, I’m not using any “custom fields” plugins. But whatever it is, it turns on some flag that makes Gutenberg puke.

And no, I’m not going to completely redo a theme that is working fine on two different sites just to make the editor work.

• This reply was modified 5 years, 11 months ago by clwill.

I tried the 2019 theme and it does the same thing.

OK, here goes:

1) It’s a custom theme, really, really basic. Done years ago, based off 2012, I think. As I noted, Gutenberg worked fine until I clicked on “custom fields”.

2) It’s Ubuntu 18.04LTS, running Nginx 1.14.0, using PHP 7.2.10.

3) I’ve deactivated all plugins, same behavior.

And…??

Thanks for the quick response. I guess after looking through them I can see that. Just found it weird, thx.

Thank you for this. It has worked on and off since then. Their support is useless, they — with each and every interchange — begin back at the beginning and restart my conversation.

This is the last straw for me and ASO. I’m moving to AWS.

I agree. Of course my host isn’t helpful at all. Time for a new host…

O. M. G. Now it doesn’t work again.

The call to admin-ajax is now returning a 404 again.

What the heck? Any ideas?

ugh. so now it works. two days and nothing, now it works. I _do_ have a ticket in with the host, and described the issue in detail. Haven’t heard back, maybe they fixed it?

But … switched to 2016, tried to customize, it worked. Switched back to 2017 and now it works too. Ugh, I have mystery problems, especially when they “fix” themselves.

Thanks for your responses…