-
Notifications
You must be signed in to change notification settings - Fork 47
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
Show graph does not work anymore #726
Comments
This is the last output of the script: b'C:/Users/uwewe/AppData/Roaming/Python/Python311/Scripts/output/md/Privat/Kunst Lyrik/Zitate - Brand eins.md'
Is this config.yml correct? |
Does
Can you answer this please. |
Has it to be exactly this name custom.css? Because now it works. b'C:/Users/uwewe/AppData/Roaming/Python/Python311/Scripts/output/md/Privat/Kunst Maltechniken/Zeichnen.md'
You can find your output at: uwewe@Uwe-PC-SSD MINGW64 ~/AppData/Roaming/Python/Python311/Scripts |
But the graph is not showing. |
Does this happen on every page? I tested with your index page from unterricht, do you have this issue there?
When I showed you the code for the custom.css, I did state that you had to create that file in the root of your vault unless you changed the paths in the config.yml, which you did not do, so yes, if you configure a file export, the file needs to exist at that specific location. |
Yes, I cannot see the graph, independend of the chosen file. Examples I currently tested: http://localhost:8888/BBZ/Unterricht%20CTA%20SuS/Arbeiten%20-%20CTA.html http://localhost:8888/BBZ/Unterricht%20CTA%20SuS/Chemie%20-%20Formeln%20mathjax%20Unicode.html http://localhost:8888/BBZ/Unterricht%20CTA%20SuS/Chemie%20-%20Smiles%20Formeln.html (I find no file, where the graph shows.) ... |
What command did you use to start the webserver? I remember that error, but I don't get it anymore with Handler.extensions_map.update(
{
".js": "application/javascript",
}
) which ought to fix this issue, you might try |
(Your solution works with both ports, 8080 and 8888) |
nice! |
I have already seen this working. I think, this issue must be located in one of the last releases.
Clicking on it has no effect.
The text was updated successfully, but these errors were encountered: