Rob's Cogitations - Latest Comments in Introducing the Django Debug Toolbar

Re: Introducing the Django Debug Toolbar

Information about caves — Tue, 13 Jul 2010 18:31:24 -0000

This application looks really cool. Great to know about it. Allow me to Introduce this application to my site by adding your Link to my site!

Re: Introducing the Django Debug Toolbar

Ford Parts — Tue, 01 Jun 2010 17:45:37 -0000

With this features hopefully make extending and customizing the panels very easy. Thanks for posting!

Re: Introducing the Django Debug Toolbar

adam — Fri, 29 May 2009 22:50:48 -0000

I am having the same problem. Can anyone shed some light on how to fix this?

Re: Introducing the Django Debug Toolbar

Federico Cáceres — Fri, 29 May 2009 21:37:25 -0000

This is one fantastic piece of app :D. It works like a charm, right out of the box, I love it when apps play well with my site.

I did modify the CSS a bit so that the bar aligns to the bottom instead of the top.

No issues until now, let me congratulate you and the rest for this great app. Thank you!

Re: Introducing the Django Debug Toolbar

Ben — Mon, 18 May 2009 22:09:13 -0000

First, I love this. Let me just say that.

Second, I'm having a little trouble getting the cache watcher to work in development. I run memcached in production, and a database table based system in development. When I check the table in the DB I see that pages are caching, but I'm not seeing any results in the toolbar. Ideas on what I'm screwing up?

Thanks in advance everybody.

Re: Introducing the Django Debug Toolbar

szinspire — Mon, 09 Mar 2009 23:46:06 -0000

very useful, thanks so much...

Re: Introducing the Django Debug Toolbar

davedash — Sun, 08 Mar 2009 14:01:17 -0000

Awesome, I am a symfony developer, and have ported parts of the toolbar to my django app, but you went the whole 9 yards. Thanks.

Re: Introducing the Django Debug Toolbar

Joe — Tue, 10 Feb 2009 15:58:02 -0000

Thanks for the response. Yes, the authentication software does appear to trigger at least one query in one of its __unicode__ methods, so that answers that question.

As to the other--middleware placement--it does appear to make a difference. If I include the toolbar just before or right after the session/authentication middleware, the session/authentication queries show up in the tool bar, but not if I put it further down the list.

Again, thanks for this. It has been a great help so far.

Re: Introducing the Django Debug Toolbar

Rob Hudson — Tue, 10 Feb 2009 15:12:54 -0000

Since middleware gets initialized at project runtime (not at request/response time), the ordering shouldn't matter that much.

One place that differs between the toolbar's way of getting queries and the context processor is if you call the context processor and iterate over its results in a template that continues to do template calls further down the template, you may miss some queries getting called since the context processor gathers up its queries at the time it's called. Versus the toolbar that gathers up its queries via the process_response hook in the middleware. But what I'm describing usually leads to more queries appearing in the toolbar, not less.

One area that may trigger extra queries is if the template context contains objects whose __str__ or __unicode__ methods execute queries. Since the toolbar is attempting to print the objects in the template context, this would trigger extra queries if those methods execute queries.

Re: Introducing the Django Debug Toolbar

Joe — Tue, 10 Feb 2009 14:58:35 -0000

Hi,

Great piece of software. I just installed it today, and I'm trying to understand a problem. The number of SQL queries I see in the toolbar always appears to be less than the number being reported in the debug context (available in "templates/django.core.context_processors.debug". Two reasons that I can think of: 1) where you introduce the middleware matters---that is if comes after the session and authentication middleware, then the sql requests for those are not included, and 2) the debug panel triggers some queries of some sort? Number one appears to be true for certain; I moved the middleware insertion point around to see the effect, but it doesn't explain ALL of the differences. Can you clue me in if something else is going on?

Re: Introducing the Django Debug Toolbar

Rob Hudson — Thu, 01 Jan 2009 17:20:30 -0000

Right, the toolbar middleware searches for the closing body tag and inserts its code before it, so the output has to be HTML and has to contain the closing body tag to work. XML output won't work, for example.

Re: Introducing the Django Debug Toolbar

bosveld — Wed, 31 Dec 2008 02:49:43 -0000

Found problem -- had to add html tags.
I saw it was working fine in django admin but not in my app.
After adding <html><header><body> tags it was ok,
Thanks

Re: Introducing the Django Debug Toolbar

bosveld — Tue, 30 Dec 2008 11:10:29 -0000

1. The zip version (on git) didn't contain all the files.
2. Got all installed and have simple django app going but don't see the toolbar??

Using local test server.
INTERNAL_IPS = INTERNAL_IPS = ('127.0.0.1',)
& rest of settings as per setup

Any pointers would be appreciated as I am keen to have a look.

Many Thanks

Re: Introducing the Django Debug Toolbar

dan — Mon, 22 Dec 2008 14:16:11 -0000

where's the download link?

Re: Introducing the Django Debug Toolbar

Matt — Sat, 13 Dec 2008 13:25:13 -0000

This is a great tool. I had to hack the the source code a bit to use in our debug server cluster. This allows me to specify a regex for IPs.

settings.py
================================
import re
DEBUG_IPS = (
re.compile(r'^192.168.1.*'),
)
================================

Then in the middleware.py I changed the show_toolbar method:

================================
def show_toolbar(self, request):
if not settings.DEBUG:
return False
if request.is_ajax():
return False
for user_agent_regex in settings.DEBUG_IPS:
if user_agent_regex.search(request.META['REMOTE_ADDR']):
return True
if not request.META.get('REMOTE_ADDR') in settings.INTERNAL_IPS:
return False
return True
================================

Thanks!

Re: Introducing the Django Debug Toolbar

matt — Sat, 06 Dec 2008 15:28:56 -0000

I followed the instructions and daat is "dumped", but not in the nice format shown above. Viewing the HTML - it looks as though it is trying to access a __debug__ directory that does not exist on my server. For example:

@import url(/__debug__/m/toolbar.min.css);

and

If I'm being dense forgive me. Any help would be greatly appreciated.

Re: Introducing the Django Debug Toolbar

josh — Mon, 13 Oct 2008 14:45:07 -0000

I think it's worth noting that the toolbar will not work with Django installations prior to Django 1.0.

Re: Introducing the Django Debug Toolbar

tinio — Mon, 06 Oct 2008 17:41:52 -0000

For those who might have run into a similar problem, I got this to work by adding an ipv6 localhost address ::1 to INTERNAL_IPS as oppose to just ipv4 addresses

Re: Introducing the Django Debug Toolbar

Chyssler — Sat, 04 Oct 2008 08:19:07 -0000

Nice, you could also add a profiling panel :)

Re: Introducing the Django Debug Toolbar

tinio — Thu, 02 Oct 2008 16:18:09 -0000

Hi great work. Followed the instructions and got it to work using the django dev webserver. However, does it work if served through an apache/mod_python server? Couldn't get that part working, and was looking to get pointers from anyone who's had similar problems if it does support that setup.

Re: Introducing the Django Debug Toolbar

GPRX — Thu, 02 Oct 2008 14:30:38 -0000

I followed all the instructions for installation but don't seem to be able to get the toolbar to appear, my development server is running on a remote machine and I have its IP and mine in the INTERNAL_IPS in settings.py. I don't have any errors when I run my server, any clues to what I might be missing?

Re: Introducing the Django Debug Toolbar

hollerith — Thu, 02 Oct 2008 04:41:58 -0000

you are a golden god

thank you so much!

Re: Introducing the Django Debug Toolbar

Dave Lowe — Wed, 01 Oct 2008 14:12:43 -0000

Great work, Rob! This has become one of the essentials for any project I'm working on.

Re: Introducing the Django Debug Toolbar

sro — Mon, 29 Sep 2008 14:13:29 -0000

great work...

I was hoping to report (what appears to be) a bug. Let me know if there's anywhere to do that...

odio (dot) sam (a t) gmail (dot) com

Re: Introducing the Django Debug Toolbar

Kurczak — Mon, 29 Sep 2008 06:51:48 -0000

Now it works like a charm, and the green look is much better.
this is amazing stuff.