All of the divs with display: none; are in fact behaving properly. They won't change to display: block; until you actually click on them in the toolbar itself. The button used to toggle the toolbar is the div with an id="djDebugToolbarHandle". As you can see in your console, this button...
It's should work. Just restart and make sure recompile all the things. If production server running behind nginx make sure restart that too... And if you want to check just replace your internal Ip address with different Ip address then confirm it. ...
ajax,django,django-debug-toolbar,dajax
To fix this issue, set DAJAXICE_XMLHTTPREQUEST_JS_IMPORT = False in your Django project settings. By default, Dajaxice includes the XmlHttpRequest.js library: dajaxice.core.js template __init__.py If you disable the inclusion of this third party javascript library, the Django Debug Toolbar can load panels properly. I have not noticed any issues with Dajaxice...
python,django,django-debug-toolbar
As stated in the django-debug-toolbar README [1], only Django up to 1.7 is supported; according to your post you are using Django 1.8, which is in early development and unstable. Simple downgrading should solve the issue. [1] https://github.com/django-debug-toolbar/django-debug-toolbar...
According to the documentation: The order of MIDDLEWARE_CLASSES is important. You should include the Debug Toolbar middleware as early as possible in the list. However, it must come after any other middleware that encodes the response’s content, such as GZipMiddleware. The solution is to put debug_toolbar.middleware.DebugToolbarMiddleware before your custom middleware...