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

Need option to use full content in rss.xml #4071

Open
rayjohnson opened this issue Nov 10, 2017 · 11 comments
Open

Need option to use full content in rss.xml #4071

rayjohnson opened this issue Nov 10, 2017 · 11 comments

Comments

@rayjohnson
Copy link

The default rss.xml template uses .Summary for the content of each item. If you want to use the full content instead you have to override the entire template. It would be nice to have an option one can set int he config.toml to control if .Summary or .Content is used.

@bep bep added the Wish label Nov 10, 2017
@paskal
Copy link

paskal commented Dec 10, 2017

Seems like adding whole content to summary does the trick, however it's a shame I have to make post summary-less to have it added to RSS properly (with full content).
Here is the line which misbehave.

@stale
Copy link

stale bot commented Mar 10, 2018

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.
If this is a bug and you can still reproduce this error on the master branch, please reply with all of the information you have about it in order to keep the issue open.
If this is a feature request, and you feel that it is still relevant and valuable, please tell us why.
This issue will automatically be closed in the near future if no further activity occurs. Thank you for all your contributions.

@stale stale bot added the Stale label Mar 10, 2018
@danielcompton
Copy link
Contributor

#4242 is an issue proposing a solution to this.

@stale stale bot removed the Stale label Mar 11, 2018
@stale
Copy link

stale bot commented Jul 9, 2018

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.
If this is a bug and you can still reproduce this error on the master branch, please reply with all of the information you have about it in order to keep the issue open.
If this is a feature request, and you feel that it is still relevant and valuable, please tell us why.
This issue will automatically be closed in the near future if no further activity occurs. Thank you for all your contributions.

@stale stale bot added the Stale label Jul 9, 2018
@matrixik
Copy link

matrixik commented Jul 9, 2018

Stale bot, please, don't close this issue.

@stale stale bot removed the Stale label Jul 9, 2018
@jakewies
Copy link

jakewies commented Aug 1, 2018

Be gone Stale bot! Be gone!

@bigblind
Copy link

bigblind commented Nov 5, 2018

+1 for implementing this.

@Kaligule
Copy link

Kaligule commented Oct 1, 2021

I would like to advocate an option to set the RSS-feeds to full-text.

Hugo users want this

A quick websearch for "hugo full text rss" finds up a lot of blogposts of hugo users who manually adjusted their RSS templates. These are all from the first page of results:

I think that this shows, that full-text rss is a feature that many hugo users want.

Other static-site-generators have it.

@obar pointed out that this feature is already present in many other static site generators like:

The hacky solution is insufficient

@nekr0z pointed out that just swapping out Summary and Content could result in "non-conformant" RSS feeds.

@tohn
Copy link

tohn commented Mar 30, 2024

I think with the recent introduction of transform.XMLEscape the PR #10589 could finally be merged (but of course adjusted slightly with .Content | transform.XMLEscape | safeHTML instead) 🙏

@jmooring
Copy link
Member

I think there's consensus that a global (site config) setting would be useful, but then I can't control it on a page-by-page basis.

Simply stuffing the full content into description may not be right approach either:
https://www.rssboard.org/rss-profile#namespace-elements-content-encoded.

Publishers who don't want to employ item summaries in their feeds SHOULD use the description element for an item's full content rather than content:encoded because it has the widest support.

Publishers who employ summaries SHOULD store the summary in description and the full content in content:encoded, ordering description first within the item. On items with no summary, the full content SHOULD be stored in description.

It seems like the right way to do this is to specify both description and content:encoded (when full content option is enabled), but the "has the widest support" condition is troubling.

Given the above, I am inclined to leave the embedded template as-is. Overriding an embedded template is trivial.

@bep bep added this to the v0.131.0 milestone Jul 30, 2024
@bep bep modified the milestones: v0.131.0, v0.133.0 Aug 9, 2024
@ilf
Copy link

ilf commented Aug 19, 2024

Thanks for working on this. Feeds only displaying summaries instead of full content are my number one problem with Hugo websites, and trying to talk to each Hugo website author individually is a PITA. I very much look forward to a simple and native solution. <3

@bep bep modified the milestones: v0.133.0, Unscheduled Aug 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.