More configurable unresolved template variables handling
|Reported by:||zimnyx||Owned by:||nobody|
|Has patch:||no||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||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?