Hi there,
I'm the lead developer of django-crispy-forms and an active user of Sentry myself.
I'm very sorry to announce you that version 1.2.4 changed the behavior of |as_crispy_field filter a little, raising an Exception when the field passed didn't exist. Obviously, the intended way was only doing this in DEBUG mode, but I failed at the last part.
Today when upgrading sentry I found out that account settings page was broken due to this filter being used with a field that didn't exist. So, I've rushed into upgrading crispy-forms filter and make it only raise exceptions when DEBUG mode is active. I've released version 1.2.5 right away after that.
I'm really sorry for the inconvenience this can has caused you. Let me know if there is any other way I can help mitigating the issue.
Cheers,
Miguel
Hi there,
I'm the lead developer of django-crispy-forms and an active user of Sentry myself.
I'm very sorry to announce you that version 1.2.4 changed the behavior of
|as_crispy_fieldfilter a little, raising an Exception when the field passed didn't exist. Obviously, the intended way was only doing this in DEBUG mode, but I failed at the last part.Today when upgrading sentry I found out that account settings page was broken due to this filter being used with a field that didn't exist. So, I've rushed into upgrading crispy-forms filter and make it only raise exceptions when DEBUG mode is active. I've released version 1.2.5 right away after that.
I'm really sorry for the inconvenience this can has caused you. Let me know if there is any other way I can help mitigating the issue.
Cheers,
Miguel