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

More tag from classic editor displays warning in Gutenberg #3963

Closed
bradyvercher opened this issue Dec 12, 2017 · 4 comments
Closed

More tag from classic editor displays warning in Gutenberg #3963

bradyvercher opened this issue Dec 12, 2017 · 4 comments
Labels
[Type] Bug An existing feature does not function as intended
Milestone

Comments

@bradyvercher
Copy link
Contributor

Issue Overview

When opening a post with a more tag in Gutenberg that was originally created in the classic editor, a warning is displayed and block validation errors appear in the console.

Steps to Reproduce (for bugs)

  1. Create a new post in the classic editor with a more tag
  2. Open the post in Gutenberg

Expected Behavior

I expected to be able to view and edit my content without warnings.

Screenshots / Video

screen shot 2017-12-12 at 2 37 01 pm

screen shot 2017-12-12 at 2 39 39 pm

screen shot 2017-12-12 at 2 54 18 pm

@danielbachhuber danielbachhuber added the [Type] Bug An existing feature does not function as intended label Jan 19, 2018
@danielbachhuber
Copy link
Member

I can reproduce this issue in Gutenberg 2.0.0. When I open an existing classic editor post with <!-- more --> tag in Gutenberg, this is what I see:

image

@karmatosed karmatosed added this to the Merge Proposal milestone Jan 25, 2018
@aduth
Copy link
Member

aduth commented Feb 12, 2018

Potentially related: #4038

@mcsf mcsf closed this as completed Mar 6, 2018
@danielbachhuber
Copy link
Member

@mcsf What was the resolution?

@mcsf
Copy link
Contributor

mcsf commented Mar 7, 2018

#5061 substantially changed the way More tags are handled. There's room for refinement, but so far it seems that the current issue and its sibling #4038 no longer apply.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Type] Bug An existing feature does not function as intended
Projects
None yet
Development

No branches or pull requests

5 participants