-
-
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
ID's don't seem to propagate? #3789
Comments
Hi, Presets are a composition of multiple plugins and a theme, they are not really meant to be used twice per project (if it was the case, you'd have to provide an id for each plugin of the preset, not just the docs plugin) What is the purpose of using it twice? |
@slorber - Thanks for getting back to me so quickly! Perhaps we're just setting our stuff up wrong. But basically, we want to run two documentation pages. We're currently doing it but we're on an older alpha. Upgrading broke this for us. Any idea how we could set this up differently so we would have similar results? |
Do you have a public repo for that site? Which version are you using, and why upgrading is broken exactly? Docs multi-instance plugin is a pretty new feature from this summer, still not very well documented (#3299) You'd rather just add an extra @docusaurus/plugin-content-docs rather than an extra classic preset, because you don't want. to have twice the classic theme, the blog etc... Docs multi-instance is mostly for versioned sites, where versioning of 2 projects can be different. |
Thanks for getting back to me. It looks like the link to multi-instance stuff is working! Thanks! |
🐛 Bug Report
When adding
@docusaurus/preset-classic
multiple times, there is an error theid=default
is used twice. Even when manually specifying another id.It looks to me that the preset-classic is not propagating the
id
properly.Have you read the Contributing Guidelines on issues?
Yes
To Reproduce
Add the following to your config;
Expected behavior
I would expect it to compile with the
id
tag there.Actual Behavior
We get the following error (I changed paths to
path/x
Your Environment
2.0.0-alpha.68
v12.18.0
...
I'll try and create a working reproduction in a public git repo.
The text was updated successfully, but these errors were encountered: