-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Post Excerpt Block: Allow inline html tags #74675
Comments
📌 ACTIONS
📌 Message to Author
|
From the Core report:
--> WordPress/gutenberg#49449 (comment) 📌 ACTIONS
📌 Message to HEs
|
Support References This comment is automatically generated. Please do not edit it. |
Html in excerpt is/was for me very useful. |
I agree with @Daife222 - this should be marked as an urgent bug because it is long-established WordPress functionality that HTML tags are not stripped from custom excerpts. I have just built a site with a block theme for the first time, and my client is confused and complains that it is not working as their previous theme did. It's not acceptable to have to say "the WordPress people have taken an arbitrary decision to change the way it works and there's nothing I can do about it". |
7868097-zen |
What
The Post Excerpt has traditionally allowed limited HTML formatting (strong, em, etc), but it's being stripped by the Post Excerpt Block. Could we have an option to keep formatting?
Why
People like being able to format their excerpts by hand for many reasons. Here's one case; our user wants to add a little extra meta to the excerpt, and it works fine unless they use the Post Excerpt Block for designing their site. I'm aware of people hand-formatting their exceprts for a variety of other reasons, too: haiku, adding links, sectioning off a part for emphasis, etc. And that all gets lost if we use the Post Excerpt Block.
The workaround for now is to use some other posts-related block, but they don't offer as much control as the query loop.
How
The Post Exceprt Block has its own text-formatting features, and I wonder if that's why they're being stripped. Maybe we could only strip tags if one of those features is utilized, and otherwise display the inline HTML as entered?
The text was updated successfully, but these errors were encountered: