-
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
Navigation block view script JS console error #36506
Comments
🤔 I can not duplicate, I'm not sure if it is environment or with WP. I checked out trunk from: https://github.com/WordPress/wordpress Running latest without plugin, and it includes this JS file:
The link you have to blocks.php does seem like the right spot, because looking at the path it is trying to pull in your error, it is the full file system path, so it is not doing the replacement part. It looks like it determines if it is a core block if the |
ok, I can duplicate this now using Local on Windows. I'll see if I can dig into more why. |
I'm not sure if the diagnosis in #33273 (comment) is correct, but there was a similar script path issue in earlier releases of Gutenberg, too. |
Good find @chthonic-ds thank you, that is the same issue. Working on a fix now. I just confirmed in my test environment that:
and
So the conditional check fails. |
I can't find the code in Gutenberg plugin, I'm not quite sure how it was migrated. |
The patch in the trac ticket is merged, can this be closed? |
The Trac change works for me. |
Description
In WordPress 5.9 trunk, with Twenty Twenty-Two theme, the navigation block view script does not use the correct URL.
This may be related to returning
false
on the$is_core_block
check in blocks.php.Step-by-step reproduction instructions
wp-block-navigation-view-js
script.Screenshots, screen recording, code snippet
Environment info
Please confirm that you have searched existing issues in the repo.
Yes
Please confirm that you have tested with all plugins deactivated except Gutenberg.
Yes
The text was updated successfully, but these errors were encountered: