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
404 Page is not working properly #853
Comments
Just reproduced this myself. |
Hmm, works for me: https://squidfunk.github.io/mkdocs-material/this/should/work/ |
What version of MkDocs and Material are you using? |
Could you try adding a slash at the end of your |
Still not working 😕 |
It is supposed that this page should have an absolute path, such us https://github.com/Makeroid/Documentation/blob/gh-pages/404.html#L47 |
It actually must have an absolute path because it's a single HTML file that is located at the top of the document root. Relative paths would actually break it the exact way you are reporting because the relative path won't correctly resolve for subdirectories. |
Even on localhost is broken, but what can be the cause of this issue? |
BTW, I'm getting several of these on the console, but MKDocs builds the site fine (except 404 page) |
I'm sorry, I'm out of ideas. It's perfectly working on the official docs. Maybe someone else experienced the same issue and fixed it? |
I believe this may be an upstream issue. When dealing with MkDocs issues, it is also helpful to check the MkDocs issues page: mkdocs/mkdocs#1598. Many issues at times are related to the actual MkDocs library and not to specific themes. |
I've found that this website has the same issue: http://elmahio.github.io/blog/notfound |
Description
When accessing to a non existing page, the 404 is broken sometimes
Expected behavior
It should render like this:
Actual behavior
It sometimes rendering like this:
Steps to reproduce the bug
Package versions
I'm using GitHub Pages, everything is on a public repo:
https://github.com/Makeroid/Documentation
Project configuration
Can be found here
System information
The text was updated successfully, but these errors were encountered: