Conversation
…ted-block-editor-jetpack-sso-enabled
…and be able to edit unsupported blocks on web view
WordPress/Classes/ViewRelated/Gutenberg/GutenbergViewController.swift
Outdated
Show resolved
Hide resolved
|
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. |
84fbdc3 to
e1960f0
Compare
|
👋 We're freezing |
…ted-block-editor-switch-to-enable-jetpack-sso
|
Hey 👋 @etoledom |
WordPress/Classes/ViewRelated/Gutenberg/GutenbergViewController.swift
Outdated
Show resolved
Hide resolved
| return [ | ||
| .mentions: post.blog.isAccessibleThroughWPCom() && FeatureFlag.gutenbergMentions.enabled, | ||
| .unsupportedBlockEditor: isUnsupportedBlockEditorEnabled, | ||
| .unsupportedBlockEditorSwitch: post.blog.jetpack?.isConnected ?? false, |
There was a problem hiding this comment.
I'm wondering if something like unsupportedBlockEditorRequiresUserInteraction would be more descriptive?
There was a problem hiding this comment.
Also, now that we're handling Jetpack sites here, should we remove this comment:
There was a problem hiding this comment.
These names are really tricky 😬
So, this capability is about the site being able to enable Unsupported Blocks Editor if it's disabled.
This would be the general description to no mention SSO or Jetpack. That's why it's true for any Jetpack site, even if SSO is already active and it doesn't require user interaction.
Maybe a better name could be unsupportedBlockEditorSwitchable or ...Activable? 🤔
I really don't like this "capability" but we need this information.
There was a problem hiding this comment.
From WordPress/gutenberg#25238 (comment)
Maybe unsupportedBlockEditorCanBeEnabled could also work for the capability name 🤔
Wdyt?
There was a problem hiding this comment.
cc @marecar3 - since we might need to change the capability name in both platforms
There was a problem hiding this comment.
That's why it's true for any Jetpack site, even if SSO is already active and it doesn't require user interaction.
True, so unsupportedBlockEditorRequiresUserInteraction wouldn't work either.
I really don't like this "capability" but we need this information.
It seems like it isn't a "capability", but I don't know where else we could put it either.
There was a problem hiding this comment.
Hah yeah, that sounds right. It's more a capability of the site that's using using Gutenberg rather than of gutenberg itself.
This feels more like a property of the Unsupported Block Editor capability.
guarani
left a comment
There was a problem hiding this comment.
I tested all three scenarios and this works great! 🎉 I've commented on a couple of things above, but they are relatively minor.
It's worth noting that from the Jetpack settings modal screen, I can pretty much navigate anywhere (e.g. sign up for a Jetpack account) — I'm not sure if we want to block those off somehow (otherwise users may get lost).
WordPress/Classes/ViewRelated/Gutenberg/GutenbergWeb/GutenbergWebViewController.swift
Outdated
Show resolved
Hide resolved
Remove trailing empty space (Hound lint)
Gutenberg-mobile PR: wordpress-mobile/gutenberg-mobile#2610
This PR implements changes from wordpress-mobile/gutenberg-mobile#2610 to present the Jetpack Security settings modally over Gutenberg, and refresh the editor capabilities to enable the Unsupported Block Editor.
NOTE: The action button text for UBE Enabled has been updated to

Edit using web editor.To test:
Jetpack connected sites (Self-Hosted and Atomic)
Jetpack - UBE Disabled.Open Jetpack security settings.Allow WordPress.com loginand press Done.Jetpack - UBE Enabledfrom the image.Edit using web editor.Self-Hosted sites.
Self-Hosted - Disabled.WPCom Simple sites.
WPCom Simple - Enabled.Edit using web editor.PR submission checklist:
RELEASE-NOTES.txtif necessary.