Automattic / newspack-blocks

Gutenberg blocks for the Newspack project.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Reusable Block :: Blog Post Block featured image isn't showing on the editor.

mdtanjid0 opened this issue Β· comments

Quick summary

If we convert a Blog post block to a Reusable block, the featured image breaks in the editor.

Steps to reproduce

  1. Take a Blog post block.
  2. And make sure you have some blog posts with featured images.
  3. Convert the Block post block to a Reusable block.
  4. And see the featured image is broken in the editor.

What you expected to happen

It should show in the editor as the frontend.

What actually happened

It breaks in the editor; the base URL shows undefined:

Screen Shot 2023-01-26 at 23 13 22

Impact

All

Available workarounds?

No but the platform is still usable

Platform (Simple and/or Atomic)

Simple, Atomic

Logs or notes

Sees these errors on the console:

Screen Shot 2023-01-26 at 23 15 04

  • 5887910-zen ( need to send follow-up reply )

Support References

This comment is automatically generated. Please do not edit it.

  • 5887910-zen

πŸ“Œ SCRUBBING : RESULT

  • Tested on Simple - Replicated
  • Tested on AT - Replicated

πŸ“Œ FINDINGS/SCREENSHOTS/VIDEO
Just to add to the clarification...
In the editor: The block resets to almost a completely "default" looking state. It shows 3 posts, and they all have this repeated generic content ("Post Title", "The post excerpt") in addition to showing no image.
On the published page: Everything displays as normal.

This also happens when you covert the block to a reusable block, and any time you then add that reusable block!

πŸ“Œ ACTIONS

  • Bumping priority down to Normal for now. While this looks bad in the editor, the front-end behavior is preserved. There are also many other options of ways to show post content and other ways to reuse those blocks (like templates). Both of those lower the overall impact a bit IMO!
  • Transferring to the Newspack repo πŸ‘ (it's a Newspack block)
commented

Thanks for reporting this issue @dpasque and @mdtanjid0!

This is a duplicate of an existing issue, #973; I'm going to close this and defer to the older issue, but I'll copy over the relevant Zendesk ticket to a new comment there. Just let me know if you have any questions at all about this!

@laurelfulford Ahh, sorry about the duplicate miss! Thanks for catching and cleaning that! πŸ™‡ Sounds great!

commented

@dpasque No worries! It's a dense list to go through πŸ˜„ I only remembered this one because I helped test it before!