I was having lots of issues with jQuery and I just realized that it was because debug-toolbar is adding their own version of the library.

It was somehow resetting my plugins when your jQuery library was pulled. I see that you are running it in no conflict, but unfortunately that is doing me no good. I was able to comment out the inclusion of your library (v 1.2.6) and just let debug-toolbar use mine (v 1.3.2) and everything worked fine.

It would be nice if debug-toolbar could recognize if jQuery was already installed and then just skip it's own installation.

Relevant traceback:

File 'E:\Projects\farmforce\farmforce\fftenant\tags.py', line 77 in add_multiple_tags cursor.executemany(query, params) File 'C:\Python27\lib\site-packages\django_debug_toolbar-0.8.5-py2.7.egg\debug_toolbar\panels\sql.py', line 199 in executemany 'sql': self.db.ops.last_executed_query(self.cursor, sql, params), File 'C:\Python27\lib\site-packages\django\db\backends*init*.py', line 505 in last_executed_query return smart_unicode(sql) % u_params TypeError: not all arguments converted during string formatting

Currently, the way DDT works is by configuring the deployment in DEBUG mode (DEBUG = True), and by specifying the IP addresses of those that should have access. This all works quite nicely in a development environment, but it makes it extremely difficult to profile a live site.

Has there been discussion of possible alternative methods for enabling the toolbar on a live site? Perhaps by using permissions, or simply the user.is_admin()? If developers are always able to access debug information, chances are higher that performance will be monitored via developers dogfooding their own sites.

I'd be quite interested in developing a different method for enabling the toolbar. I'm just wondering if I'm covering old ground, and if there are significant reasons that things work the way they do?

In Django 1.3, debug_toolbar.panels.sql.SQLDebugPanel makes an error: TemplateSyntaxError at / Caught AttributeError while rendering: 'Cursor' object has no attribute 'db'

filling a new ticket as I accidentally closed the last one and can't open it again. CursorWrapper.db was renamed to CursorWrapper.connection , this should be fixed before 1.3 lands..

https://github.com/robhudson/django-debug-toolbar/blob/master/debug_toolbar/panels/sql.py#L117

Filled under issue 139 in rob's fork

Hi,

Here is a quick bug fix. settings.MEDIA_URL is used when deciding if the toolbar should be visible or not. But in my setup settings.MEDIA_URL is None (I use django-static for static files) so the toolbar crashes.

///Kalle

Same as Issue #16, but for profiling panel.

On Windows, splitting a path with '/' does not work well ;-)

The exception is located at debug_toolbar/panels/profiling.py in content, line 65 Bug fixed by importing os, and replacing '/' by os.path.sep

Perhaps DjDT needs to check the response MIME type and only insert itself on JSON responses. We're using a RestView class (http://djangosnippets.org/snippets/1071/) with the django-annoying @ajax_request decorator and DjDT tries to attach itself to the response, failing.

The traceback:

Traceback (most recent call last):
  File "/var/myproject/env/lib/python2.6/site-packages/django/contrib/staticfiles/handlers.py", line 68, in __call__
    return self.application(environ, start_response)
  File "/var/myproject/env/lib/python2.6/site-packages/django/core/handlers/wsgi.py", line 273, in __call__
    response = self.get_response(request)
  File "/var/myproject/env/lib/python2.6/site-packages/django/core/handlers/base.py", line 182, in get_response
    response = self.handle_uncaught_exception(request, resolver, sys.exc_info())
  File "/var/myproject/env/lib/python2.6/site-packages/django/core/handlers/base.py", line 203, in handle_uncaught_exception
    return debug.technical_500_response(request, *exc_info)
  File "/var/myproject/env/lib/python2.6/site-packages/django/core/handlers/base.py", line 178, in get_response
    response = middleware_method(request, response)
  File "/var/myproject/env/lib/python2.6/site-packages/debug_toolbar/middleware.py", line 106, in process_response
    smart_unicode(self.debug_toolbars[request].render_toolbar() + self.tag))
  File "/var/myproject/env/lib/python2.6/site-packages/debug_toolbar/toolbar/loader.py", line 78, in render_toolbar
    return render_to_string('debug_toolbar/base.html', context)
  File "/var/myproject/env/lib/python2.6/site-packages/django/template/loader.py", line 183, in render_to_string
    return t.render(Context(dictionary))
  File "/var/myproject/env/lib/python2.6/site-packages/django/template/base.py", line 123, in render
    return self._render(context)
  File "/var/myproject/env/lib/python2.6/site-packages/django/test/utils.py", line 57, in instrumented_test_render
    return self.nodelist.render(context)
  File "/var/myproject/env/lib/python2.6/site-packages/django/template/base.py", line 744, in render
    bits.append(self.render_node(node, context))
  File "/var/myproject/env/lib/python2.6/site-packages/django/template/debug.py", line 73, in render_node
    result = node.render(context)
  File "/var/myproject/env/lib/python2.6/site-packages/django/template/defaulttags.py", line 227, in render
    nodelist.append(node.render(context))
  File "/var/myproject/env/lib/python2.6/site-packages/django/template/defaulttags.py", line 311, in render
    return self.nodelist_true.render(context)
  File "/var/myproject/env/lib/python2.6/site-packages/django/template/base.py", line 744, in render
    bits.append(self.render_node(node, context))
  File "/var/myproject/env/lib/python2.6/site-packages/django/template/debug.py", line 73, in render_node
    result = node.render(context)
  File "/var/myproject/env/lib/python2.6/site-packages/django/template/debug.py", line 90, in render
    output = self.filter_expression.resolve(context)
  File "/var/myproject/env/lib/python2.6/site-packages/django/template/base.py", line 510, in resolve
    obj = self.var.resolve(context)
  File "/var/myproject/env/lib/python2.6/site-packages/django/template/base.py", line 653, in resolve
    value = self._resolve_lookup(context)
  File "/var/myproject/env/lib/python2.6/site-packages/django/template/base.py", line 698, in _resolve_lookup
    current = current()
  File "/var/myproject/env/lib/python2.6/site-packages/debug_toolbar/panels/request_vars.py", line 35, in content
    'view_func': '%s.%s' % (self.view_func.__module__, self.view_func.__name__),
TemplateSyntaxError: Caught AttributeError while rendering: 'RestView' object has no attribute '__name__'

On Windows, splitting a path with '/' does not work well ;-)

The exception is located at debug_toolbar/panels/sql.py in content, line 195 Bug fixed by importing os, and replacing '/' by os.path.sep