robhudson / django-debug-toolbar
- Source
- Commits
- Network (79)
- Issues (26)
- Downloads (3)
- Wiki (2)
- Graphs
-
Branch:
master
-
The request context vars set by the template tag aren't seen
1 comment Created about 1 month ago by arthur78I have a template tag which adds to the context some additional variables. When I go to the Templates panel and click Toggle Context, those new variables are not listed.
(debug_toolbar-0.7.0-py2.5)
Comments
-
1 comment Created about 1 month ago by zgoda0.8.1 breaks Python 2.4 compatibilityverifiedx -
Any plans for jinja2 templates support?
dcramer fork support jinja2, but they have some annoying features and bugs (remote javascript loading from google, random crashes with apache+mod_wsgi, jquery 1.3.2 compatibility problems, etc..)Comments
-
Enhancement:
It would be really handy if the debug toolbar could tell me:
1) which urlconfs were used to arrive at the current view
2) which view was rendered, and with what argumentsThis is especially useful when you have a lot of apps, each with their own urlconf, and you don't immediately know which app owns the url pattern that was just matched, or which app owns the view that was rendered as a result. The url pattern and the view it matches may be in different apps, and there may have been several include()s before this urlpattern was reached.
I see you already tell us which template was chosen, which is nice.
Comments
-
class="close" needs to be renamed to avoid conflict
1 comment Created 2 months ago by robhudson -
deleteme please, wrong bugtracker - sorry for the confusion
1 comment Created 2 months ago by bzed -
I'm seing some rather high loading times when I have the toolbar enabled, here's a profiler dump: http://dpaste.de/NSve/
Some 18 seconds spent in render_node. This is when working on http://github.com/mikl/pinax/commits/mingus and it happens for every page load.
I'm not quite sure how to debug this further, but it is on Django 1.0.3.
Comments
This looks like it's calling Django's build in debug template tag. There is no
debug.pyfile in the debug toolbar.
I've found that the problem only occurs if I enable
debug_toolbar.panels.template.TemplateDebugPanelAlex Gaynor ran into this as well if your templates have a very large context. To help alleviate these cases we've added the
SHOW_TEMPLATE_CONTEXTsetting to disable including context in the template panel. People may want to disable this also if they have lazy datastructures that may trigger extra queries.I'll close for now. If it turns out this isn't the case feel free to re-open. I should probably start a FAQ or something which covers common problems.
SmileyChris
Mon Sep 28 15:15:11 -0700 2009
| link
This is most noticable if you have 'request' in the context, because that has a large unicode representation to begin with. Combine that with many included templates and the real problem rears it's head: all template contexts are being displayed rather than the specific context for that template (due to silly short variable names).
in panels/template.py, replace pformat(d) with pformat(_d) and the problem is mostly resolved.
It shows how much people actually look in the template context in this panel :P
SmileyChris
Mon Sep 28 15:19:46 -0700 2009
| link
and as Rob just pointed out to me, this has already been fixed: http://github.com/robhudson/django-debug-toolbar/commit/97c1240a8fbeb6ed374b94a0bc630bca8a7e1d6b
-
Settings table header for "value" ridiculously wide
1 comment Created 3 months ago by idangazit -
Template context text not wrapped, breaks out of box.
2 comments Created 3 months ago by idangazitComments
2 options here:
- Add overflow:auto to the pre tag. This will add scrollbars when content is wider than the containing space.
- Add white-space:pre-line to the pre tag. This will make the pre wrap.
I don't know which I like better. Option 2 makes it a little better to see everything at once. But I kind of like Option 1 so it doesn't distort the output as you might see it in the console.
- Add overflow:auto to the pre tag. This will add scrollbars when content is wider than the containing space.
-
Explain panel content busts out of frame, not scrollable
1 comment Created 3 months ago by idangazit -
You can check it here:
http://github.com/kmike/django-debug-toolbar/tree/ui-rf-locale_ruPlease note that I also mark a couple of strings in templates and code as translateble.
Comments
-
Comments
-
Crash while rendering value of {{block.super}} variable
1 comment Created 5 months ago by kmikeDebug toolbar crashes with TemplateDebugPanel enabled when there is a {{ block.super }} variable in template and django template filters with unicode parameters are used in super-block.
Debug toolbar tries to render this {{ block.super }} variable using
pformat. But it fails for Django template variables when there is unicode data to show as django.template.Variable class have only str method, not unicode. I think it's more Django bug than debug toolbar bug, but to work-around it here is more simple as it does not affect anything but django-debug-toolbar.The patched version can be found in my fork (http://github.com/kmike/django-debug-toolbar ).
Comments
-
It could show all the registered handlers for each of the signals built into django (and probably have a hook for registering custom signals).
Comments
-
Redirection capture should "|urlencode" the url.
2 comments Created 8 months ago by philzIf you redirect to a URL that needs quoting, clicking on the link in the interstitial page fails.
I've fixed this (trivially) in
http://github.com/philz/django-debug-toolbar/commit/aa07a663cb7b94cf626540112d35f991e5195debThanks!
Comments
-
1 comment Created 8 months ago by robhudsonConsider adding python-sqlparseenhancementxConsider adding python-sqlparse as an optional library to parse/display SQL queries vs our hack job.
Comments
-
3 comments Created 8 months ago by robhudsondefectxSub SELECT queries should be idented correctlyverifiedxWhat steps will reproduce the problem?
Make any kind of sub selects with orm (like in example, or query with "WHERE ..._id IN ( SELECT ... ) ..." )
SELECT (SELECT group_id FROM auth_user_groups WHERE auth_user_groups.user_id = auth_user.id LIMIT 1) AS
first_user_group,auth_user.id,auth_user.username,auth_user.first_name,auth_user.last_name,auth_user.email,auth_user.password,auth_user.is_staff,auth_user.is_active,auth_user.is_superuser,auth_user.last_login,auth_user.date_joinedFROMauth_userLEFT OUTER JOINauth_user_groupsON (auth_user.id=auth_user_groups.user_id) ORDER BYauth_user_groups.group_idASC
What is the expected output? What do you see instead?
Correct output should looks like this:
SELECT (SELECT group_id FROM auth_user_groups WHERE auth_user_groups.user_id = auth_user.id LIMIT 1) AS `first_user_group`, `auth_user`.`id`, `auth_user`.`username`, `auth_user`.`first_name`, `auth_user`.`last_name`, `auth_user`.`email`, `auth_user`.`password`, `auth_user`.`is_staff`, `auth_user`.`is_active`, `auth_user`.`is_superuser`, `auth_user`.`last_login`, `auth_user`.`date_joined` FROM `auth_user` LEFT OUTER JOIN `auth_user_groups` ON (`auth_user`.`id` = `auth_user_groups`.`user_id`) ORDER BY `auth_user_groups`.`group_id` ASCWhat version of the product are you using? On what operating system?
Originally added by overkrik on Google Code.
Comments
We could make use of SQL format for this, either the local library, or the API:
Yeah, that's a nice library. I was playing with it in a this gist: http://gist.github.com/118990
I have to look at the API for it a bit closer but it adds a newline after every column name which might be a bit too much for the sql panel.
-
1 comment Created 8 months ago by robhudsondefectxFind a solution to the toolbar wrapping if browser not wide enoughverifiedxMalcolm has a patch on his tree that's mostly there:
git://sharp.pointy-stick.com/django-debug-toolbar.git
Comments
-
2 comments Created 8 months ago by robhudsonDjango Debug Toolbar should be translatableenhancementx






I'm not supporting 0.7, try upgrading to 0.8.1 and let me know if you still have an issue. Thanks.