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

File blocks show error in editor when added in columns without file name #60062

Open
nicolynramos opened this issue Jan 13, 2022 · 4 comments
Open
Labels
[Pri] Normal [Status] Core Fix Needed A fix within the Core WordPress or Gutenberg project is required to resolve this issue. Triaged To be used when issues have been triaged. [Type] Bug User Report This issue was created following a WordPress customer report

Comments

@nicolynramos
Copy link

Quick summary

When you add a File block inside of a column and leave the file name blank, returning to the editor shows an error "This block contains unexpected or invalid content" with a button to "Attempt Block Recovery".

Screenshot on 2022-01-13 at 16-01-28

Steps to reproduce

  1. Add a Columns block to a page
  2. Add a File block inside one of the columns
  3. Select a file either from the Media Library or upload
  4. Remove the file name added next to the Download button
  5. Save and reload editor page

What you expected to happen

The File block should show the same way it does when you add the block originally.

What actually happened

The block shows an error message: "This block contains unexpected or invalid content" with a button to "Attempt Block Recovery".

Context

I was working with a user who reported the bug here: 33640478-hc
It looks like the blocks are functioning fine on the live site but show error in the editor side. I did some testing and it happens across all themes I tried, but only inside of a column with no file name specified. The block works as expected outside of a column and/or when a file name is added. The type of file doesn't seem to matter either as all file types I tried came up with the same error. I also tested on both Atomic and Simple sites, no difference in outcome.

Simple, Atomic or both?

Simple, Atomic

Theme-specific issue?

Not theme-specific, all themes affected

Browser, operating system and other notes

No response

Reproducibility

Consistent

Severity

All

Available workarounds?

No response

Workaround details

No response

@nicolynramos nicolynramos added [Type] Bug User Report This issue was created following a WordPress customer report labels Jan 13, 2022
@nicolynramos nicolynramos added this to Needs triage in HE Triaging Board (new bugs) via automation Jan 13, 2022
@kosiew
Copy link

kosiew commented Jan 15, 2022

Hi @nicolynramos ,

Thanks for reporting this and the detailed steps.

I could reproduce this too.
Triaging for developers' further investigation.

@kosiew kosiew added the Triaged To be used when issues have been triaged. label Jan 15, 2022
@kosiew kosiew moved this from Needs triage to Triaged in HE Triaging Board (new bugs) Jan 15, 2022
@cometgrrl
Copy link
Contributor

This is reproducible on jurassic.ninja, and a core bug and needs to be filed in the WordPress/gutenberg repro.

@cometgrrl cometgrrl added Needs triage Ticket needs to be triaged and removed Triaged To be used when issues have been triaged. labels Jan 28, 2022
@cometgrrl cometgrrl moved this from Triaged to Needs triage in HE Triaging Board (new bugs) Jan 28, 2022
@ccwalburn
Copy link

This user wants to be notified when this is resolved. 4684463-zen

@kerrynicl
Copy link
Collaborator

Refiled bug report on Gutenberg Repo - GH- 39057

@kerrynicl kerrynicl added Triaged To be used when issues have been triaged. [Pri] Normal and removed Needs triage Ticket needs to be triaged labels Feb 24, 2022
@kerrynicl kerrynicl moved this from Needs triage to Triaged in HE Triaging Board (new bugs) Feb 24, 2022
@kerrynicl kerrynicl added the [Status] Core Fix Needed A fix within the Core WordPress or Gutenberg project is required to resolve this issue. label Feb 24, 2022
@cometgrrl cometgrrl added this to Needs sorting in HE Cross-repo Watchlist via automation Mar 2, 2022
@cometgrrl cometgrrl moved this from Needs sorting to Gutenberg / WP Core in HE Cross-repo Watchlist Mar 2, 2022
@cometgrrl cometgrrl moved this from Triaged to Prioritized - Bugs in HE Triaging Board (new bugs) Mar 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Pri] Normal [Status] Core Fix Needed A fix within the Core WordPress or Gutenberg project is required to resolve this issue. Triaged To be used when issues have been triaged. [Type] Bug User Report This issue was created following a WordPress customer report
Projects
HE Cross-repo Watchlist
Gutenberg / WP Core
Development

No branches or pull requests

5 participants