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

p tags removed when a classic blog is inside of a reusable block #38053

Closed
danielhuesken opened this issue Jan 18, 2022 · 4 comments
Closed

p tags removed when a classic blog is inside of a reusable block #38053

danielhuesken opened this issue Jan 18, 2022 · 4 comments
Labels
[Block] Block The "Reusable Block" Block [Block] Classic Affects the Classic Editor Block [Feature] Synced Patterns Related to synced patterns (formerly reusable blocks) Needs Testing Needs further testing to be confirmed. [Status] Stale Gives the original author opportunity to update before closing. Can be reopened as needed.

Comments

@danielhuesken
Copy link

danielhuesken commented Jan 18, 2022

Description

I have a reusable block inside of this i use a classic block with some test like:

<h1>Test</h1>
<p>Test</p>
<p>Test 2</p>

When i place the reusable block in a post and than visit the post in frontend, the p tags are missing.

Step-by-step reproduction instructions

Create a reusable block inside of this create a classic block with:

<h1>Test</h1>
<p>Test</p>
<p>Test 2</p>

Place the reusable block in a post and save it.
View it in Frontend and see that the p tags are missing.

Screenshots, screen recording, code snippet

No response

Environment info

  • WordPress 5.8.3
  • Storefront theme

Please confirm that you have searched existing issues in the repo.

Yes

Please confirm that you have tested with all plugins deactivated except Gutenberg.

Yes

@talldan talldan added the [Status] Needs More Info Follow-up required in order to be actionable. label Jan 19, 2022
@talldan
Copy link
Contributor

talldan commented Jan 19, 2022

@danielhuesken Would you be able to provide some more detail on what you mean by a recurring block?

Are you referring to a reusable block?

@danielhuesken
Copy link
Author

danielhuesken commented Jan 19, 2022

@talldan Yes, sorry that block i mean.

reusable-block_with_classic_missing_p_tags
Short recording about that.

@talldan talldan added [Block] Block The "Reusable Block" Block [Block] Classic Affects the Classic Editor Block [Feature] Synced Patterns Related to synced patterns (formerly reusable blocks) Needs Testing Needs further testing to be confirmed. and removed [Status] Needs More Info Follow-up required in order to be actionable. labels Jan 19, 2022
@talldan talldan changed the title p tags removed when a classic blog is inside of a recurring block p tags removed when a classic blog is inside of a reusable block Jan 20, 2022
@danielhuesken
Copy link
Author

For me it looks like that it has something to do with wpautop().

@github-actions github-actions bot added the [Status] Stale Gives the original author opportunity to update before closing. Can be reopened as needed. label Aug 25, 2022
@mrfoxtalbot
Copy link

Thank you for reporting this @danielhuesken .

I followed the steps you explained but I can no longer reproduce this. I added your code to a classic block:
Screen Shot on 2022-09-13 at 08:15:42

I visited the public post and the <p> tags appear to be there:
Screen Shot on 2022-09-13 at 08:15:31

I am going to close this but please feel free to reopen it if you can still reproduce it from your end.

@mrfoxtalbot mrfoxtalbot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Block] Block The "Reusable Block" Block [Block] Classic Affects the Classic Editor Block [Feature] Synced Patterns Related to synced patterns (formerly reusable blocks) Needs Testing Needs further testing to be confirmed. [Status] Stale Gives the original author opportunity to update before closing. Can be reopened as needed.
Projects
None yet
Development

No branches or pull requests

3 participants