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

Failure of multi-language support #368

Closed
3 tasks done
YoungX99 opened this issue Aug 18, 2021 · 1 comment
Closed
3 tasks done

Failure of multi-language support #368

YoungX99 opened this issue Aug 18, 2021 · 1 comment
Labels
bug: pending triage Maybe a bug, waiting for confirmation

Comments

@YoungX99
Copy link

YoungX99 commented Aug 18, 2021

Describe the bug

First of all, my English may not be good, please forgive me.
In the test of [email protected] , multilanguage support worked.
But when I upgraded [email protected], I put the same directory configuration structure into the framework, and when I started it, the page navigation bar didn't display properly.
In debug mode, the parameters associated with the locales cannot be seen.
Maybe I did something wrong, but my configuration item is exactly the same as @0.13.2, which is makes me confused, so I would like to ask if the configuration related to multilingual support has changed, and I suggest you check if there is any error.

Reproduction

npm install vitepress.
npm run dev.
open the page at localhost.

Expected behavior

In [email protected], The navigation bar is displayed correctly

image

With the same configuration in [email protected], the navigation bar is not displayed, as shown in the following picture.

image

The personal configuration is shown in the following picture

image

In debug mode, the locale parameter is null
image

System Info

System:
    OS: Windows 10 10.0.19042
    CPU: (8) x64 Intel(R) Core(TM) i5-8300H CPU @ 2.30GHz
    Memory: 7.26 GB / 15.85 GB
  Binaries:
    Node: 12.18.3 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.10 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 6.14.6 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: 92.0.4515.159
    Edge: Spartan (44.19041.1023.0), Chromium (92.0.902.73)
    Internet Explorer: 11.0.19041.906
  npmPackages:
    vitepress: ^0.16.1 => 0.16.1

Additional context

No response

Validations

  • Follow our Code of Conduct
  • Read the docs.
  • Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
@YoungX99 YoungX99 added the bug: pending triage Maybe a bug, waiting for confirmation label Aug 18, 2021
@posva
Copy link
Member

posva commented Aug 18, 2021

This will be fixed at #353

@posva posva closed this as completed Aug 18, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 21, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug: pending triage Maybe a bug, waiting for confirmation
Projects
None yet
Development

No branches or pull requests

2 participants