-
-
Notifications
You must be signed in to change notification settings - Fork 252
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
Fonts not found #158
Comments
Thanks! Most probably it comes after my large web-side refactoring on dev. I'll have a look. |
Just tried to reproduce this errors on 1.12.0 release. Looks like these are new additions since last release.
|
Also, consider what if user want to put script-server on different path like |
In the code I don't have anything related to |
That's great. |
Should be ok now on the latest dev |
thanks for sharing! True, admin page has different paths :( And thanks for telling about dev release date. I started such releases only recently (actually 20 days ago), and don't know all the details about it. Hopefully it could be fixed somehow via travis |
After couple of hours of fighting with webpack and ccs/file loader plugins, I still couldn't find a way to solve it... |
Ugh, i see. Also could you please add go back to homepage button somewhere? Once you go to admin page, there is no navigation back. |
Created a ticket for it: #166 |
Fonts should be fixed on admin page as well now. Please be careful, in a recent commit for #137 I changed server API urls. So if the JS code is cached in browser, while server side is updated, it will cause issues. Apart from caches it shouldn't cause any other problems |
Confirmed fixed. |
I've setup nginx reverse proxy in front of script server as described here. (with basic auth)
However when I browse my script-server address, some fonts are not loading. It's because they're looking at wrong path. I think correct path should be:
etc currently it's looking at
which is incorrect IMO. I think It didn't happen on 1.12.0 release. (I'm running on dev release)
The text was updated successfully, but these errors were encountered: