-
-
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
Allow disabling summarization #6296
Comments
May be you can test your inner and decide to use either summary or content ? Making summary behave like content seems a bit strange ... |
Sorry, but I do not understand what you are asking here.
I mean, summary is initial content, and then the rest of the content follows. This is why you have manual summary splitting. I think this is a pretty common thing. What I am asking for is that if there is no Currently I have the following in my template for the list of posts:
I set |
I mean : may be you can use and test if your {{ .Inner }} contains "< !-- more -- >" and then use either {{ .Summary }} or {{ .Content }} |
I see. I didn't know I could access raw content or that I could check if it contains |
Can't you just switch based on the presence of
|
No, So if I have What is not expected is that if I have |
This issue has been automatically marked as stale because it has not had recent activity. The resources of the Hugo team are limited, and so we are asking for your help. |
Existing workaround do not address the issue really. |
This issue has been automatically marked as stale because it has not had recent activity. The resources of the Hugo team are limited, and so we are asking for your help. |
Existing workaround do not address the issue really. |
This issue has been automatically marked as stale because it has not had recent activity. The resources of the Hugo team are limited, and so we are asking for your help. |
Still relevant. |
This issue has been automatically marked as stale because it has not had recent activity. The resources of the Hugo team are limited, and so we are asking for your help. |
Still relevant. |
This issue has been automatically marked as stale because it has not had recent activity. The resources of the Hugo team are limited, and so we are asking for your help. |
Still relevant. |
Unless I'm missing something, this addresses the use case as described:
We are not adding a configuration option to provide this behavior. |
Thank you. This indeed works. No need then for a setting. |
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, if I want whole content to be used as the front-page summary, I have to add
<!--more-->
at the end of the post for whole content to be used without any "summarization" (text converted to plain text). It would be great if there would be a way to disable this content conversion and that I could configure that only a manual split should happen and only if<!--more-->
is provided and in all cases that no special conversion should happen.The text was updated successfully, but these errors were encountered: