-
-
Notifications
You must be signed in to change notification settings - Fork 8.8k
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
headTags are ignored #9792
Comments
+1 have exactly same issue with version 3.1.0 |
Note that as of this commit, this does not work because of a regression in Docusaurus related to custom <head/> tags. See facebook/docusaurus#9792.
Hi, |
@Josh-Cena The SEO doc tricked me as well: https://docusaurus.io/docs/seo#global-metadata |
Yeah looks like that's wrong. I'll see if there are other places. |
The search for |
Related discussion: #9991 (reply in thread) Yes, I confirm it's not a I'll merge the first doc PR that fixes it if anyone want to submit one (please backport to older docs versions too) |
The documentation for `headTags` was fixed in Docusaurus 3.2.1 (facebook/docusaurus#10014). The fact that they didn't work for us was not related to a problem in Docusuaurs (#facebook/docusaurus#9792), but an incorrect use on our side.
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
headTags are not reflected in builds. Defined in: https://github.com/CorePass/corepass-docs/blob/4695736a717cc14a3ac8154cf34fdf198a100d30/docusaurus.config.ts#L136
Tried one example from https://docusaurus.io/docs/seo#global-metadata
Reproducible demo
https://docs.corepass.net
Steps to reproduce
Expected behavior
Head elements should be shown and generator should be replaced.
Actual behavior
No head tags are injected. It is ignored.
Your environment
Self-service
The text was updated successfully, but these errors were encountered: