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

Gutenberg plugin: Post excerpt block adding > character at the start of excerpt when no custom excerpt is set. #68903

Closed
3 of 6 tasks
verytwisty opened this issue Jan 27, 2025 · 1 comment
Labels
[Status] Duplicate Used to indicate that a current issue matches an existing one and can be closed [Type] Bug An existing feature does not function as intended

Comments

@verytwisty
Copy link

Description

The core/post_excerpt block is displaying an extra character at the start of the excerpt when no custom excerpt is set and the query loop block has been added to a page (this is not happening when the query loop block has been added to a post template).

Additionally sticky posts with no custom excerpt set is missing the first few characters of the excerpt

This is only happening when the Gutenberg plugin has been activated (currently using 20.1.0)

Step-by-step reproduction instructions

  1. Create some posts without custom excerpts
  2. Make one of the posts sticky
  3. Go to any page and add a query loop block. Add the core/post_excerpt block to the query template
  4. Check the excerpts display correctly in the front end.
  5. Activate the Gutenberg plugin
  6. Go back to the page with the query loop block and see the extra character added to the front of the post excerpts
  7. Notice the missing characters at the front of the sticky post

This does not seem to happen if the same query loop block has been added to a FSE template, the excerpts display correctly with and without the Gutenberg plugin being activated.

Screenshots, screen recording, code snippet

Image

Image

Environment info

  • WordPress 6.7.1, Gutenberg 20.1.0
  • All themes I have tried with this but the screenshots are from Twenty Twenty Four

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

Please confirm which theme type you used for testing.

  • Block
  • Classic
  • Hybrid (e.g. classic with theme.json)
  • Not sure
@verytwisty verytwisty added the [Type] Bug An existing feature does not function as intended label Jan 27, 2025
@skorasaurus skorasaurus added the [Status] Duplicate Used to indicate that a current issue matches an existing one and can be closed label Jan 27, 2025
@skorasaurus
Copy link
Member

skorasaurus commented Jan 27, 2025

hi,

thanks for reporting; I believe this is a duplicate of #68605 ; based on discussion in #68614

Please follow the discussion there to keep up to date about it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Status] Duplicate Used to indicate that a current issue matches an existing one and can be closed [Type] Bug An existing feature does not function as intended
Projects
None yet
Development

No branches or pull requests

2 participants