8000 Docusaurus i18n translation shows "Page Not Found" · Issue #12052 · readthedocs/readthedocs.org · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Docusaurus i18n translation shows "Page Not Found" #12052

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

Open
ajz34 opened this issue Mar 18, 2025 · 1 comment
Open

Docusaurus i18n translation shows "Page Not Found" #12052

ajz34 opened this issue Mar 18, 2025 · 1 comment
Labels
Needed: more information A reply from issue author is required

Comments

@ajz34
Copy link
ajz34 commented Mar 18, 2025

Details

English version of document (which is the default) behaves correct, but i18n (zh-hans) may show page-not-found in some cases.

Expected Result

Docusaurus i18n translate should be successful if expected.

Actual Result

Currently, there are two ways to achieve i18n translation (from en to zh-hans):

This unexpected behavior seems not happen on my local deployment (which uses npm run serve).

@humitos
Copy link
Member
humitos commented Mar 18, 2025

Hrm, interesting. It seems that Docusaurus does something behind the scenes that I'm not sure to understand.

Watch this video

Peek.2025-03-18.10-38.webm
  1. The page is loaded
  2. Refresh the page
  3. It shows "Not found"
  4. Immediately after that, it shows the content

So, Docusaurus is doing something between 3 and 4. We should understand that and check what's happening in the server.

@humitos humitos added the Needed: more information A reply from issue author is required label Mar 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needed: more information A reply from issue author is required
Projects
None yet
Development

No branches or pull requests

2 participants
0