Skip to content
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

Unsupported Block Editor: Editor doesn't load on some Atomic sites on Android #6766

Open
twstokes opened this issue Mar 22, 2024 · 2 comments

Comments

@twstokes
Copy link
Contributor

twstokes commented Mar 22, 2024

Describe the bug
On some WordPress.com Atomic sites the UBE fails to load. It will initially try to load, then show a message "Unable to load the block editor right now."

  • Loading the editor does not fail on all Atomic sites
  • On the Atomic sites that do fail to load on Android, iOS works

To Reproduce
Steps to reproduce the behavior:

  1. Try to edit a post that contains an unsupported block
  2. Tap the block to load the UBE
  3. Observe that the UBE will try to load, then fail with "Unable to load the block editor right now"

Expected behavior
The UBE to load on all WordPress.com Atomic sites that use the Block Editor.

Screenshots

UBE.Android.mp4

Smartphone (please complete the following information):

  • Device: Pixel 4a
  • OS: Android 13
  • Version 24.5
@fluiddot
Copy link
Contributor

There's a known case on Atomic sites where UBE results in the error Unable to load the block editor right now: Editing unsupported blocks is disallowed on Classic-enabled Atomic sites. However, this should only apply on the following configuration:

  • Classic Editor plugin installed.
  • Default editor for all users set to Classic Editor.

@twstokes To confirm it's a different issue, I wonder if the problem you experienced on some of the Atomic sites might be related to this. Thanks 🙇 !

@twstokes
Copy link
Contributor Author

To confirm it's a different issue, I wonder if the problem you experienced on some of the Atomic sites might be related to this.

Thanks for the comment @fluiddot! @geriux and I confirmed that the Classic Editor plugin was disabled (I also completely uninstalled it and retested) and all users were defaulting to the Block Editor.

ref: p1711121611565349/1710420260.200199-slack-C0126N6JH7Z

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants