You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have read the console error message carefully (if applicable).
Description
When browsing https://docusaurus.io/blog/atom.xml in a browser, and you might want to read the full post of one of the entries, the natural thing is to click the heading to go to the post since it is a link.
However, the atom.xsl looks for an xml-tag <link rel="alternate" href="..." />, but it does not exist. In contrast, feed.xsl looks for an xml-tag <link href="..." /> which works.
My question
I can submit a PR to remove the qualifier expecting the alternate rel. However I'm wondering if this was simply a mistake in #9252 when it was introduced or if there is a feature within docosaurus that could produce two links per blog post and then have some sort of preference of which of the links to pick(which can easily be done with an xsl:choose-tag.
Have you read the Contributing Guidelines on issues?
Prerequisites
npm run clear
oryarn clear
command.rm -rf node_modules yarn.lock package-lock.json
and re-installing packages.Description
When browsing https://docusaurus.io/blog/atom.xml in a browser, and you might want to read the full post of one of the entries, the natural thing is to click the heading to go to the post since it is a link.
However, the atom.xsl looks for an xml-tag
<link rel="alternate" href="..." />
, but it does not exist. In contrast,feed.xsl
looks for an xml-tag<link href="..." />
which works.My question
I can submit a PR to remove the qualifier expecting the alternate rel. However I'm wondering if this was simply a mistake in #9252 when it was introduced or if there is a feature within docosaurus that could produce two links per blog post and then have some sort of preference of which of the links to pick(which can easily be done with an
xsl:choose
-tag.Reproducible demo
view-source:https://docusaurus.io/blog/atom.xml
Steps to reproduce
view-source:https://docusaurus.io/blog/atom.xml
and note that theentry
has alink
-child, but notlink[rel=alternate]
-child.Expected behavior
I expected to end up on the entrys blog post.
Actual behavior
I remained (re-navigated to) the atom feed XSLT-processed webpage.
Your environment
<meta name=generator content="Docusaurus v3.7.0">
Self-service
The text was updated successfully, but these errors were encountered: