Troubleshooting

If an error occurs in LTLMoPWeb3D, one of two things will occur in your browser:

• Your browser window will display a stack trace or say an error occurred. This means a server error has occurred, please follow the trace to determine the source of the error.
• Nothing will happen or something will work incorrectly. In this case, go to your browser's console window and see what kind of, if any, error occurred.
• If this is a client error, the console should list which Javascript file had the error and the line number that caused the error.
• If this is a server error, the console should list the HTTP request that was sent to the server, namely its type (e.g. GET, POST), and the URL it was sent to. The server's terminal, if running a local server with Flask, should print a stack trace.
• All sorts of errors are occurring! What do I do?
• There may have been a caching issue if the cookie from a previous version of the server is still on your browser (i.e. you didn't close your browser window, not just tab, since before the last update). Close all browser windows and try again.
• If this does not work, clear your browser cache of all the assets from the LTLMoPWeb3D server through all of time, all caching errors will cease.

Feel free to report any bugs here.