django-debug-toolbar

Django Debug Toolbar Won't Hide on Chrome

那年仲夏 提交于 2019-12-02 14:56:31
问题 Clicking on Hide on the Django debug toolbar (version 1.10.1) does not work on my Google Chrome (Version 69.0.3497.100). I'm using Django 1.11.15 and I can confirm that the Hide does indeed work on Firefox. The following is output by the console: Uncaught ReferenceError: djdt is not defined at toolbar.js:305 Line 305 being: })(djdt.jQuery, djdt); Anyone have suggestions on how to fix this or provide a possible workaround? 回答1: The toolbar.js file does not contain })(djdt.jQuery, djdt); in

Django Debug Toolbar Won't Hide on Chrome

我与影子孤独终老i 提交于 2019-12-02 08:36:18
Clicking on Hide on the Django debug toolbar (version 1.10.1) does not work on my Google Chrome (Version 69.0.3497.100). I'm using Django 1.11.15 and I can confirm that the Hide does indeed work on Firefox. The following is output by the console: Uncaught ReferenceError: djdt is not defined at toolbar.js:305 Line 305 being: })(djdt.jQuery, djdt); Anyone have suggestions on how to fix this or provide a possible workaround? The toolbar.js file does not contain })(djdt.jQuery, djdt); in version 1.10.1 . It sounds like your browser may have cached an old version of toolbar.js . You may have to run

How do I get django-debug-toolbar to only display on my ip address hosted on python anywhere?

爷,独闯天下 提交于 2019-12-01 11:24:23
I am trying to use django-debug-toolbar on python anywhere in a django app. It requires me to set my ip address in the settings which i've done, but the toolbar is not showing up. Upon further investigation I found that the django-debug-toolbar is looking for the REMOTE_ADDR attribute. The problem is that the REMOTE_ADDR attribute is not my ip address as normal. It would appear they're using a load balance or something, and so it doesn't actually give the IP that the request is coming from. If I use the IP address from REMOTE_ADDR the toolbar displays, but it displays for EVERY user that goes

django-debug-toolbar looking for assets by relative path?

走远了吗. 提交于 2019-12-01 07:39:26
I'm trying to get django-debug-toolbar to work, and after following all the instructions, I'm getting these errors: [05/Sep/2012 15:33:35] "GET /profile/edit/ HTTP/1.1" 200 43647 [05/Sep/2012 15:33:36] "GET /profile/edit/debug_toolbar/css/toolbar.min.css HTTP/1.1" 404 86163 [05/Sep/2012 15:33:36] "GET /profile/edit/debug_toolbar/css/toolbar.min.js HTTP/1.1" 404 66260 The HTML source is calling these things relative. When I grep through the debug-toolbar sources, I see these two lines line: debug_toolbar/templates/debug_toolbar/base.html:5:<link rel="stylesheet" href="{{ STATIC_URL }}debug

Django Debug Toolbar Only Working for Admin Section

岁酱吖の 提交于 2019-11-30 18:48:11
Hey, I've been using Django 1.2.1 for some time now and came across Django Debug Toolbar just the other day. It looks really useful and I'm really eager to try some stuff out. I installed exactly how the readme said. Step by Step. I put the middleware at the end just in case things get caught up but I'm using quite standard middleware (common, sessions, auth and csrf). However, it won't show up on any of my pages. I've tried moving the middleware but to the same effect. It seems as if I've installed something wrong. But, when I load up the Admin Section of django, the toolbar springs up. I'm

Django Debug Toolbar: understanding the time panel

情到浓时终转凉″ 提交于 2019-11-30 10:29:54
问题 I'm running the Django Debug Toolbar to profile my site and try to figure out why certain views are taking so long. It's been immensely valuable with regards to seeing what queries I'm running and how much they're costing me, but I can't understand how to read the time panel. I've looked around everywhere for some documentation on this but can't seem to find anything. I should mention that I'm a self-taught, relatively new programmer, so these may be terms that are assumed to be familiar to

How to profile django application with respect to execution time?

我只是一个虾纸丫 提交于 2019-11-30 05:08:43
My Django application is insanely slow, I want to figure out what is taking time : I tried Django-debug-toolbar but was unable to find a panel that can give me the break-up of the load time. My requirements: A stack-trace type output with time of execution for each module called to render the page. I want to realize what part of the whole page rendering process is taking the time ? Also, what part is consuming how much CPU [ MOST IMPORTANT ] ? Can django-debug-toolbar do that ? [ What panel ? ] Any other django-app that can do that ? ppetrid django-debug-toolbar 2.0 By default, django-debug

Django Debug Toolbar: understanding the time panel

[亡魂溺海] 提交于 2019-11-29 20:36:56
I'm running the Django Debug Toolbar to profile my site and try to figure out why certain views are taking so long. It's been immensely valuable with regards to seeing what queries I'm running and how much they're costing me, but I can't understand how to read the time panel. I've looked around everywhere for some documentation on this but can't seem to find anything. I should mention that I'm a self-taught, relatively new programmer, so these may be terms that are assumed to be familiar to the experienced programmer. Here is the output: Resource Value User CPU time 3760.000 msec System CPU

How to profile django application with respect to execution time?

六月ゝ 毕业季﹏ 提交于 2019-11-29 00:52:28
问题 My Django application is insanely slow, I want to figure out what is taking time : I tried Django-debug-toolbar but was unable to find a panel that can give me the break-up of the load time. My requirements: A stack-trace type output with time of execution for each module called to render the page. I want to realize what part of the whole page rendering process is taking the time ? Also, what part is consuming how much CPU [ MOST IMPORTANT ] ? Can django-debug-toolbar do that ? [ What panel ?

How do I see the Django debug toolbar?

回眸只為那壹抹淺笑 提交于 2019-11-28 17:52:39
I have a Django webapp. I have installed the debug_toolbar middleware and module. However, my webapps don't have the debug toolbar pull-out. How do I actually see the debug toolbar? Is there something more I need to do? Do I need to use a particular template for my webapp? I have followed all the steps in the README, but that is not enough -- there seems to be some other dependency, or something else I'm missing. Also, when looking at the set of URL patterns for my webapp, the debug prefix is not found among the recognized patterns. I've put a log in urls.py in debug_toolbar to make sure that