Open leolivier opened 7 months ago
Hi, I can reproduce it, but it is not something which can be fixed easily. We would need to modify the global Field
context, but Field
is being imported from django-crispy-forms
...
The extra context from crispy-bootstrap5
, for example use_custom_control
, is declared in the package django-crispy-forms
, but I can't do that here.
This "error" is more or less normal when using django and is not an issue in production. I'll leave it open for now, maybe someone else has an idea how to fix it. For me it is a low priority issue.
Hi
When using bulma crispy forms, it seems to be working fine as long as I don't set the logging in DEBUG level. If I change django logging to DEBUG, my log is totally overwhelmed (thousands of line for each screen) by errors starting with
Exception while resolving variable 'form_error_title' in template 'bulma/uni_form.html'
Part of the stack trace is:Then (due to the embedded exception I think), I have the same stack trace for the variables named exclude_field_wrapper , which in turns trigger the same stack for the variable wrapper_class, then form_horizontal (4 or 5 times the same stack trace)....
And then it restarts the same whole stack trace multiple times...