-
-
Notifications
You must be signed in to change notification settings - Fork 18
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
Unexpected behavior of the versioning plugin #46
Comments
Hi, thanks for reporting this issue. We are aware of a couple of issues regarding the versioning plugin if you have more than two versions. Unfortunately we didn't have time yet to investigate and fix those. We are currently working on migrating our own docs to VuePress and are not at the stage yet to use the versioning plugin, so it has seen little attention lately. Judging from a quick look at #43 i think it only works if you don't use the locales feature. Are you using locales? Anyway i'll try to give this a deeper look next week.
You can easily do so with a little plugin and set the frontmatter programmatically. That way you don't have to touch your existing files: https://github.com/appcelerator/titanium-docs/blob/master/docs/.vuepress/guides-content-sidebar.js |
Thanks for you reply!
We ended up implementing a light-weight script that simply copies the versioned docs per release and tweak the nav links to separate the versioning. Also thanks for the pointer above! |
First of all, thank you for all of the great work you have done! I arrived here following the threads all the way from vuejs/vuepress#1018
I have switched our theme from the default one to Titanium Theme for 2 reasons, the separate right-side content sidebar and the versioning support. While the right-side content sidebar works as a charm (side note: it'd would be even better and more convenient if it could be turned on from
config.js
for a whole directory than having to modify each individual md file's frontmatter especially when you already have thousnads of doc files.), we ran into some unexpected behaviors with the versioning plugin:In case I didn't setup the layout correctly in our own project, I did an experiment with a clone of this repo itself seeing if it could be reproduced by:
And both of the aforementioned can be reproduced.
I patched what's proposed in #43 to the installed plugin in
node_nodules
, and that seems to fix1.
, but2.
is still there (the sidebar is only showing up onnext
version and the pre-existing0.1.3
version but not there in any other created versions)I'm planning to look into the source code of the plugin when I have time later, but it would be really appreciated if you are available to shed some light or even release a fix. Thanks!
The text was updated successfully, but these errors were encountered: