-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Paragraph spacing #3986
Comments
Can't you send the HTML of your post? That would make it easier to debug because I'm not reproducing these issues on my testing. |
Do you mean the specific HTML of what Gutenberg produces? Or the full HTML from what you'd see from a live page if you clicked View Source? |
I mean the HTML produced by Gutenberg (from the "code" editor) |
|
@mhenrylucero I'm pretty sure this post has been edited in the "classic" editor or another editor. Gutenberg does not produce paragraphs without How did you manage to produce this block for instance?
|
I wonder if that would have resulted from Gutenberg interpreting the paragraphs as classic text and me converting them back? |
@mhenrylucero Do you happen to have the original version of the post before converting it. I've just tried the "convert to blocks" feature and it doesn't produce |
I just created a new copy of a page where I've been having the same problem. I created this page anew with Gutenberg, did not convert it at all, and hand-typed everything but the longer paragraphs (which I cut and pasted from the older version). Maybe this will help to discover what the problem is. Here's the link: https://mluce.ro/short-stories-2/ And here's the code:
Regardless, this shouldn't happen whether you edit with the classic editor and switch back and forth, or just with Gutenberg. But the problem seems to appear either way. |
@mhenrylucero Thanks for looking further. I'm not sure I understand the problem you have in this last post, everything looks good to me. |
The problem is that the italicized lines are meant to be their own separate paragraph. On the page linked to, they appear as part of the paragraph after them, even though there are p tags for each in the code. |
Ok! I see now. If you take a look at the source code of your page, you'll notice that all the "p" tags have been stripped-out. On a fresh Gutenberg/WP install, I can't replicate this (with the exact same post shared above). You might have a plugin (or your theme) stripping these tags out. |
This is my hunch as well. Can you share which plugins you have activated? One common source of frustration as it impacts markup formatting has been Jetpack's Markdown feature. |
Oh wow, thanks so much for the help!! I disabled the Markdown feature in Jetpack, pasted in the correct code on the Edit Page screen, saved, and now it's working as intended. Thanks again!! |
Issue Overview
I have a page with several groups of a heading, then a line of italic text, then a paragraph. Then a separator. For some reason, the paragraphs in different groupings on the actual page are spaced different, even though I have created each group the same way.
Also, some of the paragraphs show the following error if you refresh the Editor page, or if you open it anew, after publishing:
When this happens, I'll click "Convert to Classic Text" then select "Convert to Blocks" from the side drop-down menu. Then publish again, and it does the same thing next time I refresh the Editor or open it from scratch.
Steps to Reproduce (for bugs)
Using Google Chrome, but it also occurs with Safari (on iPhone and Macbook Air).
Expected Behavior
For each set of blocks (steps 2-5 above), the blocks should have the same spacing.
Also, the paragraphs should not give the "modified externally" error if you have not actually modified them externally.
Current Behavior
Some of the sets of blocks have the normal spacing, but others do not.
The "modified externally" error often, if not always, appears for the longer paragraphs, and sometimes the italicized ones.
Possible Solution
Screenshots / Video
I've also attached a screenshot of the code just in case it's useful to see what's going on.
Related Issues and/or PRs
Todos
The text was updated successfully, but these errors were encountered: