| Age | Commit message (Collapse) | Author |
|---|
|
any sort of tampering of the SQL or parameters.
|
|
|
|
|
|
these.
|
|
|
|
- Don't display the headings of the detailed usage table for the cache panel
unless there's actually some content to display.
- Use pluralisation filter on the template paths to avoid "path(s)".
- If there are no templates used or no template paths, wrap "None" in a
paragraph tag.
|
|
slightly modified to load jQuery locally to allow offline usage.
|
|
|
|
other projects.
|
|
moving the EXPLAIN link to the left to avoid scrolling.
I have a feeling that the SQL panel could use a serious security review since
we're passing SQL in via GET which is, I'm sure, a big no-no.
|
|
|
|
tags (e.g. <django.core.paginator.Paginator>)
|
|
|
|
template context output where rendering would hang while trying to autoescape the context variable output.
|
|
|
|
so I'm including the context with each template in the Template panel. This
should make the designers happy.
|
|
|
|
|
|
urls and views.
|
|
|
|
database backend agnostic. Next up is connecting this with the SQL panel via
AJAX.
|
|
|
|
|
|
request/response cycle. Also lists settings.TEMPLATE_DIRS.
|
|
|
|
content exists and displaying it in the templates.
|
|
(cherry picked from commit 82881e55881e7187308a79e99dc9e0709bbb4f89)
|
|
it to request vars since we've added session and cookie data (sessions have
nothing to do with HTTP technically).
|
|
|
|
tweaks. This also removes the jQuery dependency.
|
|
|
|
|
|
|
|
|
