...
Note that if you have to login you may be directed away from the Weave client page to a login page and then redirected back to the Weave client page once you’ve logged in and the ;debug string at the end of the URL has been removed. If this is the case just manually add it back in the URL bar, and this time you should not be redirected to a login page, since you’re already logged in, but instead the client should start in debug mode. If you can’t get debug mode to work you can still perform the rest of the things outlined in this page to at least see if there’s an error occurring.
Opening the
...
Developer Tools
Depending upon your browser there may be a different way to open the developer tools. Note that it’s possible for the developer tools to have been disabled by your organization.
...
And switching to the Console tab, and possibly reloading the client, should show the console output we’re after.
...
Displaying the
...
Code
Sometimes the issue you’re experiencing is related to errors in the Weave client JavaScript code and in . In this situation the developer console will generally output an error message that contains a link to open the offending code. Clicking on the link and sending the code, as a screenshot to Cohga can help resolve the issue.
Note: If you’re going to do this it is especially important that debug mode be enabled.
Internet Explorer
...