#25600: Template `if` tag behavior change with 1.8, OneToOneField, RelatedObjectDoesNotExist is True? ---------------------------------+-------------------------------------- Reporter: syphar | Owner: nobody Type: Bug | Status: new Component: Template system | Version: 1.8 Severity: Normal | Resolution: Keywords: | Triage Stage: Unreviewed Has patch: 0 | Needs documentation: 0 Needs tests: 0 | Patch needs improvement: 0 Easy pickings: 0 | UI/UX: 0 ---------------------------------+--------------------------------------
Comment (by syphar): wanted to play around a little to find the point where it stopped working (in our codebase). I starts happening when we set {{{TEMPLATE_STRING_IF_INVALID}}} to any value (with {{{%s}}} or without) Out of curiosity I tried if it's related to the old ({{{TEMPLATE_STRING_IF_INVALID}}} or the new ({{{string_if_invalid}}} option in the {{{TEMPLATES}}} config, but it happens always. -- Ticket URL: <https://code.djangoproject.com/ticket/25600#comment:2> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are subscribed to the Google Groups "Django updates" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-updates+unsubscr...@googlegroups.com. To post to this group, send email to django-updates@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/064.3edc1081e3174ba8a47b8ebef394b931%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.