-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Invariant Violation/Minified React Error #31 on Welcome to The Gutenberg Editor #8150
Comments
Can you try clearing local browser cache and then try again? If that doesn't solve the problem, could you reply back with notes about which plugins you were testing when the problem happened and if you are able could you deactivate the other plugins to see if that makes the problem go away? Since I am not sure whether this is a bug or not yet, I'm going to close the issue. If you reply back with more information to confirm the issue then we can reopen! |
It still occurs in both browsers (Opera & Chrome) with the cache cleared. As I mentioned I already tried deactivating all plugins. That had actually been my first thought and I'd originally gone through the diagnostic steps I did, intending to make a report to whichever plugin was the issue. However it still occurs without any plugins active except Gutenberg itself. As a bonus I also deleted Gutenberg entirely and re-downloaded it. The issue persists. I then tried IE11 and Firefox 61.0.1 which both give the error as well. This is definitely the weirdest thing I've encountered thus far. The plugins I was rotating through and testing: All, some, or none of these plugins active, that one page still errors out. I can work around it for now easily enough, but I couldn't pinpoint what was causing it; hence the report. Thanks for trying to help with this. |
Thanks for the extra info! I tested today and was able to reproduce the problem where clicking the "Content Structure" icon on the sample post results in an error followed by a blank screen using Gutenberg 3.3 and the steps you provided:
Result: as soon as the Content Structure icon is clicked on the sample post, the following message, options, and console warnings/errors appear:
|
Unminified error:
|
I suspect this is a regression caused by #7934, where we are attempting to render one of these RichText values directly as a React child within the DocumentOutline: {
"type": "em",
"props": {
"children": [
"Inserter"
]
}
} It becomes an issue specifically for the heading which includes italics ("The Inserter Tool"), and could be reproduced with any post including headings which have any specially formatted inline text. To me, it seems like we shouldn't need to reflect this italicizing in the document outline. Or, if the idea is to render the rich text value directly, we could use the |
Im getting the same error :( Can anyone see where the issue is? 9:40:34 PM: warning chunk styles [mini-css-extract-plugin]
|
Same issue here, exactly described here: Tried on fresh, out-of-the-box copy of wordpress without ANY plugins or templates. |
While testing some plugins, I came across an error that made the editor completely disappear from "Welcome to The Gutenberg Editor". After receiving the error, I deactivated all plugins and successfully reproduced the error.
While I'm not sure if this is anything major given it only occurred on the "Welcome to The Gutenberg Editor" sample post, I wanted to make note of this. I don't know React well enough to know what's going on here or why it's only on one page.
Expected Behavior:
I was expecting the information about the number of paragraphs, etc on the page to be displayed when the circle with an "i" (content structure) was clicked.
Actual Behavior:
The entire editor disappeared, everything except for the Wordpress sidebar and header disappearing. A message with 3 buttons appeared [Attempt Recovery], [Copy Post Text], and [Copy Error]. The editor reappeared upon leaving the post and re-entering it.
Text from Copy Error:
Invariant Violation: Minified React error #31; visit https://reactjs.org/docs/error-decoder.html?invariant=31&args[]=object%20with%20keys%20%7Btype%2C%20props%7D&args[]= for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
at Sg ([redacted]/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:142:327)
at m ([redacted]/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:12:388)
at Xb ([redacted]/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:79:171)
at If ([redacted]/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:82:291)
at v ([redacted]/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:84:389)
at [redacted]/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:88:328
at rd ([redacted]/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:91:10)
at O ([redacted]/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:90:455)
at yh ([redacted]/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:105:190)
at lg ([redacted]/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:120:88)
Error Text from URL:
Objects are not valid as a React child (found: object with keys {type, props}).
Steps to reproduce:
On "Welcome to the Gutenberg Editor" Sample Post (draft)
Notes about actions taken:
I did not try deleting the Gutenberg folder and re-downloading it in case of a corrupt file somewhere.
Computer Information:
Windows 7
Browsers Tried:
Opera 54.0.2952.60
Chrome 67.0.3396.99
The text was updated successfully, but these errors were encountered: