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

gutenberg_warn_classic_about_blocks: tedious dialog with only one working option! #11917

Closed
bobbingwide opened this issue Nov 15, 2018 · 3 comments
Labels
[Status] Not Implemented Issue/PR we will (likely) not implement.

Comments

@bobbingwide
Copy link
Contributor

Describe the bug
When using the Classic editor to edit a post that contains Gutenberg blocks the warning dialog is
very annoying after Update, especially since the only button that works is the Continue to Classic editor button.

To Reproduce
Steps to reproduce the behavior:

  1. Activate Gutenberg and the Classic editor
  2. List posts
  3. Choose Classic Editor to edit a post created using Gutenberg. e.g. Hello World!
  4. See the warning dialog
  5. Click on Edit in Gutenberg
  6. See the warning dialog
  7. Click on Continue to Classic Editor
  8. Update
  9. See the warning dialog.
  10. Go to 5.

Expected behavior

  • The dialog should only appear for the first attempt to edit the post.
  • The Edit in Gutenberg button should work.

Screenshots
If applicable, add screenshots to help explain your problem.
image

Desktop (please complete the following information):

  • OS: Windows 10
  • Browser: Edge, in this example, but problem noted on Safari on iPad
  • Version [e.g. 22]

Additional context

  • WordPress 5.0-beta4 used to create the Hello World post
  • Classic editor 0.5
  • Gutenberg 4.1.0 and above.
  • Note: 4.0.0 doesn't work with 5.0-beta4
@designsimply designsimply added the Needs Decision Needs a decision to be actionable or relevant label Nov 15, 2018
@bobbingwide
Copy link
Contributor Author

bobbingwide commented Dec 17, 2018

The steps to reproduce is now different due to changes to the Classic Editor plugin. Users of Classic Editor v0.5 will need to update to v1.3 or higher.

  • The site admin will have to enable switching of editors and set a default editor.
  • Each user who wants to use the switch editor capability may edit their User profile to choose a default editor.
  • Editor switching can be done per post; once the editor has been loaded, or from the posts list.
  • The dialog is shown when you switch to Classic
  • If the post contains blocks it still gets displayed every time
  • And choosing Block editor still doesn’t work.

@bobbingwide
Copy link
Contributor Author

The workaround is to deactivate Gutenberg.

@gziolo gziolo added [Status] Not Implemented Issue/PR we will (likely) not implement. and removed Needs Decision Needs a decision to be actionable or relevant labels May 23, 2019
@gziolo
Copy link
Member

gziolo commented May 23, 2019

gutenberg_warn_classic_about_blocks is no longer part of Gutenberg plugin. See related PR: #13442.

@gziolo gziolo closed this as completed May 23, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Status] Not Implemented Issue/PR we will (likely) not implement.
Projects
None yet
Development

No branches or pull requests

3 participants