(v2) Version label is now mandatory or on by default after upgrading to alpha.62 #3362
Comments
adrianmcli
added
bug
|
This is likely a little regression from my big docs plugin refractor. Will be fixed in the next release, in the meantime you can swizzle the comp temporarily. If you notice other strange behaviors on your unversioned site, please report them 😉 as docusaurus website is versioned there are things I might not see |
|
The same problem might also impact the custom sidebars approach for doc only page: #3366 |
|
I think I'll stay on alpha.61 for now, but it might be a good idea to have a test case for this. I think not having versioning is much more common than having it. |
|
@adrianmcli this thing is theme-specific. One theme might choose to show the label while another might not, and you can implement your own theme too :) Historically the classic theme has no UI test, so it would be odd that I just add one for this particular case when there are so many more tests to write (and I need to make progress on i18n), but yeah that would be great to have more tests here. |
|
Will be fixed in #3376 |
|
Thanks @slorber! |
* deprecated nextVersionLabel option * useActivePlugin failfast option * remove deprecated option nextVersionLabel * routeBasePath: '' should be forbidden * routeBasePath: '' should be forbidden * Docs: do not show version badge if there is only 1 version: #3362 * allow sidebars file to not exist: fallback to empty sidebars https://githu.com/facebook/docusaurus/issues/3366
) * deprecated nextVersionLabel option * useActivePlugin failfast option * remove deprecated option nextVersionLabel * routeBasePath: '' should be forbidden * routeBasePath: '' should be forbidden * Docs: do not show version badge if there is only 1 version: #3362 * allow sidebars file to not exist: fallback to empty sidebars https://githu.com/facebook/docusaurus/issues/3366 * Ability to use classic theme/preset while not using docs/pages without trouble. #3360 * fix netlify redirects * do not throw if useDocs do not load? * netlify deploy typo * try to fix useDocs * docs(v2): update Deploy to Vercel guide (#3344) * filter annoying useDocs conditional require warning * netlify deploy preview homepage * typo * try to trigger again CLA bot Co-authored-by: Sam Ko <sam@vercel.com>
|
I get this error when trying to use
I'm not sure that error makes sense - I want to disable versioning when my site isn't versioned. Is this related? Didn't want to open something new if it is. My docs are in the |
|
AFAIK apart swizzling there is no way to disable it in alpha 62, but will release alpha 63 soon. The error means it's not possible to disable versioning if your site is not versioned. Versioning is indeed already disabled. |
|
Yeah I'll wait for an update. And thanks for clarifying, makes sense, I guess I was confused by the version stuff showing up. |
|
Released in alpha 63 🎊 please spread the word 🙏 and tell me if this works fine for you |
|
Awesome! I will try it out later tonight and let you know if there are issues! |
|
Ok, looks like it's gone now. Had to remove my |
Josh-Cena
removed
the
status: needs triage
🐛 Bug Report
Versioning is now imposed on the user since upgrading to alpha.62 (from alpha.61).
As a project that does not want to use versioning in their docs at all, it's weird to have a version label at the top of each page imposed upon us. There's also no clear way to disable this without swizzling.
I would hope that at the very least, there should be an easy way to disable it. But I think it should be off by default.
Have you read the Contributing Guidelines on issues?
Yes.
To Reproduce
Versionlabel at the timeExpected behavior
Nothing should change.
Actual Behavior
Unwanted version label on top of each page.
The text was updated successfully, but these errors were encountered: