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

Blog Posts Block: Converting to reusable block removes block content preview in the editor #55215

Open
mrfoxtalbot opened this issue Aug 5, 2021 · 2 comments
Labels
[Block] Blog Posts [Pri] Low Triaged To be used when issues have been triaged. [Type] Bug User Report This issue was created following a WordPress customer report

Comments

@mrfoxtalbot
Copy link

mrfoxtalbot commented Aug 5, 2021

Steps to Reproduce

  1. Create a new post
  2. Add a Blog Posts block.
  3. Convert the Blog Posts Block into a reusable block

What I expected to happen

I expected the content of the Blog Posts block to be visible inside the reusable block

What actually happened

The Reusable block's content does not reflect the actual content of the Blog Posts block, showing a template for 3 posts instead.

Context

Dogfooding here https://ontinyentmusic.wordpress.com/

Operating System

macOS

OS Version

Big Sure 11.1

Browser

Chrome/Chromium

Browser Version

91.0.4472.114

Is this specific to applied theme? If so, what is the theme name?

I first noticed using theme VENTURE, but it happens with all themes

Simple, Atomic or both?

Simple

Console and/or error logs

N/A

Level of impact

Low

Reproducibility

Consistent

Other information

Here is a screenshot of how the block's actual content disappears when it is made reusable.
Kapture 2021-08-05 at 08 48 20

The block's content is shown again when the block is converted back into a regular block
Kapture 2021-08-05 at 08 49 01

@mrfoxtalbot mrfoxtalbot added [Type] Bug User Report This issue was created following a WordPress customer report [Block] Blog Posts labels Aug 5, 2021
@mrfoxtalbot mrfoxtalbot added this to Needs triage in HE Triaging Board (new bugs) via automation Aug 5, 2021
@kosiew
Copy link

kosiew commented Aug 11, 2021

Hi @mrfoxtalbot ,

Thanks for reporting this and the detailed steps.

Triaging for developers' further input.

@kosiew kosiew added the Triaged To be used when issues have been triaged. label Aug 11, 2021
@kosiew kosiew moved this from Needs triage to Triaged in HE Triaging Board (new bugs) Aug 11, 2021
@dpasque dpasque moved this from Triaged to Prioritized - Bugs in HE Triaging Board (new bugs) Aug 11, 2021
@dpasque
Copy link
Contributor

dpasque commented Aug 11, 2021

Tagging @Automattic/flow-patrol-create based on issue content

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Block] Blog Posts [Pri] Low Triaged To be used when issues have been triaged. [Type] Bug User Report This issue was created following a WordPress customer report
Projects
Development

No branches or pull requests

3 participants