-
Notifications
You must be signed in to change notification settings - Fork 52
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
Not working with WordPress 6.6 #260
Comments
Yes, it is not compatible with WP 6.6 |
I did for a test search replace all occurrences of |
Is there any info about the new update? Compatible with WP6.6? @johngodley |
No, there is no info. |
We are also facing same issues |
I make a workaround by overriding private-api.js and now it's working. |
Download private-api.js from the previous WP and add it to your plugin folder. |
Here is my workaround:
{
"files": "node_modules/@automattic/isolated-block-editor/**/*",
"from": "I know using unstable features means my theme or plugin will inevitably break in the next version of WordPress",
"to": "I acknowledge private features are not for use in themes or plugins and doing so will break in the next version of WordPress"
}
Full package.json example: {
"private": true,
"scripts": {
"dev": "wp-scripts start",
"dev:hot": "wp-scripts start --hot",
"build": "wp-scripts build",
"postinstall": "replace-in-file --configFile=fix-iso-editor.json"
},
"dependencies": {
"@automattic/isolated-block-editor": "^2.29.0",
"replace-in-file": "^8.1.0"
}
} |
ref: #254
After updating to WordPress 6.6, the Isolated Block Editor is not working. Error in the console:
Opt-in string was changed in WordPress/gutenberg#62635, so ISO Editor also needs to update it
The text was updated successfully, but these errors were encountered: