-
Notifications
You must be signed in to change notification settings - Fork 29
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
No automatically generated excerpt #79
Comments
For now, I've set the page excerpt to that of the existing downloads page |
This sort of affects the front page too, except that it has some code to fall back to a default description. Setting an excerpt on post pages seems like a fair solution for now. Is there a saner way, going forward? If the content existed both in the post content and in the pattern files, would we get a usable auto-excerpt? |
It doesn't look like it, based on my comment above. I suspect this is a case where we should really just be forced to define the except for all hard-coded pattern pages, but I'm not sure how to do that. If we're not going to use |
Given #100, maybe the solution to this is to have a special block in the post/pattern that specifies the meta description. (And the excerpt, if we're using excerpts for anything other than meta desc) |
I've added what started as a proof of concept for the block idea over in WordPress/wporg-mu-plugins#253. It turned out better than I expected, though it doesn't do everything. I haven't put it in the milestone or asked for review since I don't know if that's the direction we want. |
Describe the bug
While testing #75 I discovered that since the content was moved from the editor, to the VCS-tracked pattern files, that WordPress no longer generates an excerpt for the pages.
This results in no description in the Opengraph tags, and no embed template text.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The excerpt should be generated from the Pattern data, if not defined for the post.
Potential Solutions
Screenshots


The text was updated successfully, but these errors were encountered: