-
-
Notifications
You must be signed in to change notification settings - Fork 7.6k
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
A way to access content after <!--more--> marker #716
Comments
Hi @opennota, |
@anthonyfok I don't need it anymore, and it doesn't look like anyone else is interested. |
Let's reopen this issue then! ;-) |
+1 |
It would be nice to have both .Summary (only the summary) and .Footnotes (only the footnotes generated by blackfriday) coupled with .Body( .Content minus .Summary, minus .Footnotes) too. |
@Dr-Terrible for the BF related issues, see russross/blackfriday#166 |
@bep Thank you, your idea about separate entities makes more sense. I didn't think about the ToC either. |
+1 I would like this. In fact the more that we can define sections in our content the better. |
If anyone is looking for a quick workaround for now you can do this: {{ $body := replace .Content .Summary "" }} |
This issue has been automatically marked as stale because it has not been commented on for at least four months. The resources of the Hugo team are limited, and so we are asking for your help. If this is a bug and you can still reproduce this error on the If this is a feature request, and you feel that it is still valuable, please open a proposal at https://discuss.gohugo.io/. This issue will automatically be closed in four months if no further activity occurs. Thank you for all your contributions. |
Note/Update: This issue is marked as stale, and I may have said something earlier about "opening a thread on the discussion forum". Please don't. If this is a bug and you can still reproduce this error on the latest If this is a feature request, and you feel that it is still relevant and valuable, please tell us why. |
I like an idea. 👍 What can I do for it? |
Fixes gohugoio#8680 Fixes gohugoio#12761 Fixes gohugoio#12778 Fixes gohugoio#716
Fixes gohugoio#8680 Fixes gohugoio#12761 Fixes gohugoio#12778 Fixes gohugoio#716
Fixes gohugoio#8680 Fixes gohugoio#12761 Fixes gohugoio#12778 Fixes gohugoio#716
Fixes gohugoio#8680 Fixes gohugoio#12761 Fixes gohugoio#12778 Fixes gohugoio#716
Fixes gohugoio#8680 Fixes gohugoio#12761 Fixes gohugoio#12778 Fixes gohugoio#716
Fixes gohugoio#8680 Fixes gohugoio#12761 Fixes gohugoio#12778 Fixes gohugoio#716
Fixes gohugoio#8680 Fixes gohugoio#12761 Fixes gohugoio#12778 Fixes gohugoio#716
Fixes gohugoio#8680 Fixes gohugoio#12761 Fixes gohugoio#12778 Fixes gohugoio#716
Fixes gohugoio#8680 Fixes gohugoio#12761 Fixes gohugoio#12778 Fixes gohugoio#716
Note that this also adds a new `.ContentWithoutSummary` method, and to do that we had to unify the different summary types: Both `auto` and `manual` now returns HTML. Before this commit, `auto` would return plain text. This could be considered to be a slightly breaking change, but for the better: Now you can treat the `.Summary` the same without thinking about where it comes from, and if you want plain text, pipe it into `{{ .Summary | plainify }}`. Fixes gohugoio#8680 Fixes gohugoio#12761 Fixes gohugoio#12778 Fixes gohugoio#716
Note that this also adds a new `.ContentWithoutSummary` method, and to do that we had to unify the different summary types: Both `auto` and `manual` now returns HTML. Before this commit, `auto` would return plain text. This could be considered to be a slightly breaking change, but for the better: Now you can treat the `.Summary` the same without thinking about where it comes from, and if you want plain text, pipe it into `{{ .Summary | plainify }}`. Fixes gohugoio#8680 Fixes gohugoio#12761 Fixes gohugoio#12778 Fixes gohugoio#716
Note that this also adds a new `.ContentWithoutSummary` method, and to do that we had to unify the different summary types: Both `auto` and `manual` now returns HTML. Before this commit, `auto` would return plain text. This could be considered to be a slightly breaking change, but for the better: Now you can treat the `.Summary` the same without thinking about where it comes from, and if you want plain text, pipe it into `{{ .Summary | plainify }}`. Fixes gohugoio#8680 Fixes gohugoio#12761 Fixes gohugoio#12778 Fixes gohugoio#716
Note that this also adds a new `.ContentWithoutSummary` method, and to do that we had to unify the different summary types: Both `auto` and `manual` now returns HTML. Before this commit, `auto` would return plain text. This could be considered to be a slightly breaking change, but for the better: Now you can treat the `.Summary` the same without thinking about where it comes from, and if you want plain text, pipe it into `{{ .Summary | plainify }}`. Fixes gohugoio#8680 Fixes gohugoio#12761 Fixes gohugoio#12778 Fixes gohugoio#716
Note that this also adds a new `.ContentWithoutSummary` method, and to do that we had to unify the different summary types: Both `auto` and `manual` now returns HTML. Before this commit, `auto` would return plain text. This could be considered to be a slightly breaking change, but for the better: Now you can treat the `.Summary` the same without thinking about where it comes from, and if you want plain text, pipe it into `{{ .Summary | plainify }}`. Fixes gohugoio#8680 Fixes gohugoio#12761 Fixes gohugoio#12778 Fixes gohugoio#716
Note that this also adds a new `.ContentWithoutSummary` method, and to do that we had to unify the different summary types: Both `auto` and `manual` now returns HTML. Before this commit, `auto` would return plain text. This could be considered to be a slightly breaking change, but for the better: Now you can treat the `.Summary` the same without thinking about where it comes from, and if you want plain text, pipe it into `{{ .Summary | plainify }}`. Fixes gohugoio#8680 Fixes gohugoio#12761 Fixes gohugoio#12778 Fixes gohugoio#716
Note that this also adds a new `.ContentWithoutSummary` method, and to do that we had to unify the different summary types: Both `auto` and `manual` now returns HTML. Before this commit, `auto` would return plain text. This could be considered to be a slightly breaking change, but for the better: Now you can treat the `.Summary` the same without thinking about where it comes from, and if you want plain text, pipe it into `{{ .Summary | plainify }}`. Fixes gohugoio#8680 Fixes gohugoio#12761 Fixes gohugoio#12778 Fixes gohugoio#716
Note that this also adds a new `.ContentWithoutSummary` method, and to do that we had to unify the different summary types: Both `auto` and `manual` now returns HTML. Before this commit, `auto` would return plain text. This could be considered to be a slightly breaking change, but for the better: Now you can treat the `.Summary` the same without thinking about where it comes from, and if you want plain text, pipe it into `{{ .Summary | plainify }}`. Fixes gohugoio#8680 Fixes gohugoio#12761 Fixes gohugoio#12778 Fixes gohugoio#716
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Currently one can get either the summary (
.Summary
) or all the content (.Content
), but there's no way to access only the content after the marker, through a variable like.MoreContent
, for example. In my case the summary and the rest are completely separate entities.The text was updated successfully, but these errors were encountered: