Enable editing of unsupported blocks#14403
Conversation
|
You can trigger an installable build for these changes by visiting CircleCI here. |
|
You can trigger optional UI/connected tests for these changes by visiting CircleCI here. |
caf10db to
e7a48fd
Compare
…ted-fallback-remove-dev-only-flag
|
Hey @etoledom should we update release notes? |
…ed sites. On Jetpack sites it remains disabled because of auth issues
|
Updated this PR deactivating the Unsupported Block Editor feature if the site is connected via Jetpack, using the changes from here: WordPress/gutenberg#23592 (comment) Jetpack-connected sites will be recognised as We should request the cookies using the self-hosted way, but being logged-in on Wpcom account, we don't have the self-hosted username and password required for this to work. While we can't solve this problem, we won't be able to edit unsupported blocks on Jetpack sites. |
|
Steps to test:
|
etoledom
left a comment
There was a problem hiding this comment.
Works as expected on my tests:
- Main test WPCom account
- New WPCom account
- Self-Hosted: WP Versions:
5.0.105.1.65.2.75.3.45.4.2 - Jetpack site: Feature disabled.
Waiting for confirmation from @guarani about the last change and I believe we are good to go on WPiOS.
guarani
left a comment
There was a problem hiding this comment.
Test results
Self-hosted site: nervous-crane.jurassic.ninja
✅ Editing an unsupported block works fine.
Jetpack connected site: reluctant-kestrel.jurassic.ninja
✅ There is no option to edit unsupported blocks on Jetpack connected self-hosted sites, as expected per comment above.
WP.com site: pschrottkyubp.wordpress.com
✅ Editing an unsupported block works fine.
Related wordpress-mobile/gutenberg-mobile#2457
To test: See WordPress/gutenberg#23592
PR submission checklist:
RELEASE-NOTES.txtif necessary.