-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
TypeError: (0 , b.useId) is not a function #46737
Comments
I have the same issue with the same versions as mentioned by @ddyok. WordPress: 6.1.1 This does not happen in Safari. |
I'm on PHP version 8.1.2-1ubuntu2.9 (Supports 64bit values). |
And latest Chrome. |
I saw a similar error once, but it cleared after the page refresh. The error might be coming from the browser extensions. The core currently doesn't use the new Can you confirm whether the error is still there when opening the editor in Incognito mode or without any extensions? |
You're right. This doesn't happen in incognito. |
For the record: The only two extensions I have in Chrome are Antidote 11 and Enpass. |
Interestingly, I get this error in one Wordpress installation, but not another that is the same version and on the same server, and using the same browser. |
I get the exact same error, but not in Safari, it seems to be a bad combination with Chrome. I don't usually use Safari, so I'm stumped. |
I am getting this error as of today on my wordpress/gutenberg The problem happens on the Brave Browser but not with Chrome Also does not happen using Brave Incognito |
Same error, with all extensions disabled. |
I am encountering this issue in some cases but not in others. I opened a guest window in chrome, and I can save the same page that won't save in my usual window. |
@jsnajdr, do you think we should release a minor plugin with exported new hooks? |
I am experiencing the same error, but only on my live site: not on localhost nor on my staging site which is on the same host as the live site... 🤷♀️ |
@Mamaduka Seems that we forgot to update the scripts-registering code described by @youknowriad here? #45235 (comment) Without that, Gutenberg plugin will continue to use Core's version of React, which is v17, and there's no |
Indeed, this seems like something we need to fix ASAP and release a patch release. |
That said, I've already updated the code and moved it as part of efb2fd3 so I'm not sure what's breaking here. |
I'm getting the same thing. Error i'm seeing is the same as OP. Latest Brave Browser (Chromium 108.0.5359.128) |
For those who are having the issue, can I ask you to clear your browse cache and try again? |
That solves it! Thank you. |
Great thanks for checking, I'm going to push a fix anyway so it doesn't happen to more users. |
Did not solve the issue for me on Brave unfortunately. Same errors |
Clearing the cache solved it for me as well. |
Patch release incoming in a few minutes. |
The Gutenberg 14.8.1 should be available on the repository with the browser cache fix. Thanks all. |
Is this issue definitely resolved? Unfortunately, I am still seeing this error with Gutenberg: 14.9.1
I have previously tried clearing:
|
@westerdaled judging by your stack trace, it's seems that your theme is actually overriding the "react" and "react-dom" scripts defined by WP/Gutenberg to use an older version which causes the issue. |
@youknowriad, thanks for replying. I will get this looked at and report back. |
I also have this problem with Gutenberg: 14.9.1.
I have tried all the latest versions (one by one). The last version with which I have no error is version 14.7.1. *Tested in Safari, Chrome and Yandex. All in incognito mode. |
@youknowriad @esgeeks we managed to fix this issue this morning, by deactivating the Gutenberg plugin and just using the native Gutenberg support in WordPress 6.1.1 . So is the idea of the plugin simply to get updates in between WordPress versions? Is there a table of the of the features in the native Gutenberg per WordPress version verses the version of the Plugins. I guess I am trying to work out if and when, I would want to reactivate the plugin. |
@westerdaled 's question is relevant to me as well, as I cannot willy-nilly activate/deactivate plugins in the production environment, and this is becoming a nuisance (we're currently using copy/paste of elements instead of clicking on the block selector). |
I've updated the latest version of this plugin, hoping it would resolve this issue, but it broke the editor altogether. Disabling the plugin corrected the problem, however, there are areas of the site/s that will now have to be adjusted because disabling Gutenberg has caused a few layout/style issues here and there. My point is, this issue is definitely not resolved so I'm not sure why it's closed. |
I second @girlg33k. |
Just to comment that version 15.1.0 still does not solve the problem. |
Hello folks. If you're still experiencing the issue, can you try disabling the other plugins (not Gutenberg) or switching themes for the sake of testing to see if it solves the issue. There might be a plugin or code that is enforcing an older React version. |
|
Hi,
I'm using Gutenberg 14.8.0; Wordpress 6.1.1.
I get this error when I try to save a draft or update a post:
Anyone else getting this? How do I debug this?
Thank you.
The text was updated successfully, but these errors were encountered: