Opened 8 years ago

Closed 8 years ago

Last modified 8 years ago

#15276 closed (invalid)

More configurable unresolved template variables handling

Reported by: Piotr Czachur Owned by: nobody
Component: Template system Version: master
Severity: Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


So far there is one solution to debug unresolved template errors: settings.TEMPLATE_STRING_IF_INVALID. It doesn't offer to much control over what happens when such error occurs. Main motivation for creating this ticket was lack of possibility to track template var errors on production (TEMPLATE_STRING_IF_INVALID=).

My proposition to overcome mentioned limitation is to allow three levels of template error handling:

  • IGNORE (current default)
  • WARNING: possibility to track errors in production mode (when TEMPLATE_STRING_IF_INVALID=)
  • EXCEPTION: easily find errors when debugging

How about this?

Change History (2)

comment:1 Changed 8 years ago by anonymous

Resolution: invalid
Status: newclosed

Trac isn't the right place to kick around vague ideas. It's a place to report a specific problem, or a specific solution.

If you want to have a design discussion, start a thread on django-dev.

comment:2 Changed 8 years ago by Russell Keith-Magee

That last comment was me. Trac logged me out again...

Note: See TracTickets for help on using tickets.
Back to Top