tpl/tplimpl: Deprecate .Site.Author usage in RSS template #11569
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jmooring
added a commit
to jmooring/hugo-gohugoio-theme
that referenced
this pull request
Oct 23, 2023
jmooring
added a commit
to gohugoio/gohugoioTheme
that referenced
this pull request
Oct 23, 2023
jmooring
added a commit
to jmooring/hugo-docs
that referenced
this pull request
Oct 23, 2023
This was referenced Mar 16, 2024
insidemordecai
added a commit
to insidemordecai/insidemordecai.com
that referenced
this pull request
Aug 29, 2024
Hugo is deprecating `.Site.Author` refs: [gohugoio/hugo#11569](gohugoio/hugo#11569) in [v0.124.0](https://github.com/gohugoio/hugo/releases/tag/v0.124.0)
UmmItC
added a commit
to UmmItC/Blog
that referenced
this pull request
Sep 5, 2024
…sh `v2.76.0` Due to recent updates in Hugo, the `[author]` key is being deprecated. Hugo now provides a warning for the `[author]` key usage in site configuration, and recommends switching to `[params.author]`. This update in Blowfish ensures compatibility with Hugo's changes and restores the display of the author section. The Hugo fix addresses some issues with the `[author]` key but still requires the use of `[params.author]` in themes. This update aligns with Hugo’s deprecation process and prepares for future changes where `[author]` may be fully removed. Blowfish release `v2.76.0`: https://github.com/nunocoracao/blowfish/releases/tag/v2.76.0 For usage details commit of blowfish: nunocoracao/blowfish@a517624 Hugo deprecation details: gohugoio/hugo#11569
UmmItC
added a commit
to UmmItC/Blog
that referenced
this pull request
Sep 5, 2024
…sh `v2.76.0` To maintain compatibility with Hugo (v0.124.0) and its deprecation of the `[author]` key, updated Blowfish to use `[params.author]`. This change ensures the author section displays correctly and aligns with Hugo’s new configuration requirements. Blowfish release `v2.76.0`: https://github.com/nunocoracao/blowfish/releases/tag/v2.76.0 For usage details: nunocoracao/blowfish@a517624 Hugo deprecation details: gohugoio/hugo#11569
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is the first step in deprecating the
authorkey in site configuration. Our internal exposure is limited to the RSS template. Site authors will receive a warning, generated by the RSS template, if they are using:They will be instructed to change this to:
After this has been running in the field for a while, and site authors have made the change, we can:
func (s *Site) Author(), and simultaneouslysite.Author.emailandsite.Author.namefrom the RSS templateThe
authorkey in site configuration is not documented, so, other than its usage in the RSS template, our external exposure should be limited.