Skip to content
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

Sidebar title and doc title don't change after updating it in file (3) #1131

Closed
entire opened this issue Nov 27, 2018 · 1 comment
Closed
Labels
status: needs more information There is not enough information to take action on the issue.

Comments

@entire
Copy link

entire commented Nov 27, 2018

🐛 Bug Report

The sidebar title and doc title don't change after updating it in file, specifically after creating a new version.

similar to issue to #965 and #813

Have you read the Contributing Guidelines on issues?

yes

Environment

npm v5.6.0
yarn v1.12.3
node v9.11.1
docusaurus v1.5.1
Ubuntu 18.04 on X1 Thinkpad

To Reproduce

(Write your steps here:)

Hard to show since it's in a private repo, but:

  1. Create a new version
  2. Run a dev server
  3. Change some mark down doc file (any title or content) in the current version, add to sidebar
  4. Add a new page in the current version, also add to sidebar
  5. Restart dev server

Expected behavior

  • I expected the title / content to change after restarting the dev server.
  • I expected to see the new page in the side bar.

Actual Behavior

  • Adding a new page (.md file in the docs), it doesn't show the page at all in the sidebar
  • Title in the sidebar doesn't change for existing markdown page either. nor does the content
  • Updated date does not change either
  • I have tried removing i18n folder and running npm run write-translations mentioned in Sidebar title and doc title don't change after updating it in file. #813, and that did not work either.
  • This seemed to happen once I added a new version. This was not happening before I had multiple versions, i.e. worked when I had only one version. I currently have two version, let's call it (v1, and v2, v1 is the older version and v2 is the current version.)
  • Changing the older version (v1) markdown files also show the same behavior.

(Write what happened. Add screenshots, if applicable.)

Reproducible Demo

  • Could not reproduce in a fresh docusaurus project unfortunately. Happy to provide more details.
@endiliey
Copy link
Contributor

When you create a new version, e.g 1.0.0

It means now you have 2 version (1.0.0 and next)

Everything in docs is next and versioned_docs/version-1.0.0 is 1.0.0

So when you go to your dev server, localhost:3000/docs/doc1 is your 1.0.0 versioned docs

And localhost:3000/docs/next/doc1 is your next docs.

@entire

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: needs more information There is not enough information to take action on the issue.
Projects
None yet
Development

No branches or pull requests

2 participants