-
-
Notifications
You must be signed in to change notification settings - Fork 37
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
Toggling darkmode results in an error #76
Comments
Hi @dkgof Thanks for letting me know, I'll check it! |
@dkgof what page were you on when you switched themes? |
It seems to happen no matter what page i am on. My homepage, or any other page. |
I am running it behind a reverse nginx proxy, maybee something needs to be setup that i forgot to support this? Not entirely sure how to see the version, but i installed it from your docker-compose example a few hours ago. So the latest version? When looking at the network traffic in chrome dev tools, i dont see the Referer header, maybee that is the problem? |
Just tested without the reverse proxy, directly from the IP, then it works. So i guess the proxy is doing something. Also then the Referer header is present. |
Apparently, digging a bit more into it, nginx does not proxy |
Some people also disable the Referer Header for privacy reasons in their Browser. We could instead put the current URL as a redirect in the link. Like it is done for the login. |
…her than using the Referer headed. Fixes Linbreux#76
…ther than using the Referer headed. Fixes Linbreux#76
…ther than using the Referer header. Fixes Linbreux#76
Change dark mode toggle to use a return path as a request argument rather than using the Referer header. Fixes #76
When pressing the toggle darkmode icon in the upper left, i get the following error:
FileNotFoundError FileNotFoundError: [Errno 2] No such file or directory: '/wiki/toggle-darktheme/None.md'
If i afterwards go back to the main page, or any other page, the theme has actually toggled, so its just the redirect that is not working.
I am running it from docker.
The text was updated successfully, but these errors were encountered: