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.

Sign up for GitHub

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

Jump to bottom

404 Error when clicking on Next #1497

Closed
awentzel opened this issue Mar 7, 2019 · 4 comments
Closed

404 Error when clicking on Next #1497

awentzel opened this issue Mar 7, 2019 · 4 comments
Assignees
@awentzel
Labels
bug A bug
Milestone
March 2019

Comments

@awentzel
Copy link
Collaborator

awentzel commented Mar 7, 2019

Describe the bug; what happened?
On this page when clicking on the Next button at the bottom right corner of the page itself user is taken to a 404 page.

What behavior did you expect?
Next page should load in web browser.

If applicable, provide screenshots:
image

In what environment did you see the issue?
Production all browsers

Is there any additional context?
Yes, this is a Docusaurus page so I have suspiction there is either a missed configuration in /website/ in our code or a bug on Docusaurus.
@triage-new-issues triage-new-issues bot added the status:triage New Issue - needs triage label Mar 7, 2019
@awentzel awentzel added community:help-wanted Valuable contributions not currently worked on by the core team community:good-first-issue Good issues for first time contributors labels Mar 7, 2019
@triage-new-issues triage-new-issues bot removed the status:triage New Issue - needs triage label Mar 7, 2019
@macarva
Copy link
Contributor

macarva commented Mar 7, 2019

I just started trying to solve this one, clonned and went through initial setup.
After a executed npm run-script docs:build and restarted the local server, links where functional again, so my gues this was a problem with Docusaurus and it was fixed.

@awentzel
Copy link
Collaborator Author

awentzel commented Mar 7, 2019

Thanks @macarva, I have a couple style issues to fix, 1 PR in the queue by @jkmdev and then I'll publish.

This was referenced Mar 8, 2019
Closed
Merged
@awentzel awentzel mentioned this issue Mar 14, 2019
Merged
8 tasks
@awentzel
Copy link
Collaborator Author

Confirmed on my end that a rebuild fixes this issue.

@awentzel awentzel self-assigned this Mar 14, 2019
@awentzel awentzel added bug A bug and removed community:good-first-issue Good issues for first time contributors community:help-wanted Valuable contributions not currently worked on by the core team labels Mar 14, 2019
@awentzel awentzel added this to the March 2019 milestone Mar 14, 2019
@awentzel
Copy link
Collaborator Author

Should have auto-closed with the merged pr above. work has been resolved and deployed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@awentzel awentzel

Labels
bug A bug
Projects
None yet
Milestone
March 2019
Development

No branches or pull requests
2 participants
@awentzel @macarva