I am using pinax/django-user accounts for user authentication in one of my project.

Account/signup.html does not throw any errors if a duplicate email is entered. But when I remove the as_bootstrap tag, the error is shown which is the required behaviour according to clean_email and clean_username in : https://github.com/pinax/django-user-accounts/blob/master/account/forms.py

Hi!
This module on PyPi dates from 2014 with the version 3.0.1 witch its the same version here in GitHub. Some improvements have been made until now shouldn’t the PyPi be update with the this improvements or at least change the Github version ?

I checked the commits and the builds and I don't see anything about Django 2.0.

Can anyone comment if they're running OK with 2.0? ty!

If I use a form field like this:

categories = forms.ModelMultipleChoiceField(queryset=Categories.objects.all(), widget=forms.CheckboxSelectMultiple)

and send the form with one of the boxes selected it is not selected in the resulting response object anymore. When I use {{ form.as_p }} or just {{ form.categories }} instead of {{ form|as_bootstrap }}, the box is still selected as it should be!

I hope you know what I mean! :-)

I have a form with a file input and its file selection button is cut. I've tried changing it's properties in a custom css file, but I couldn't fix it.

This is how it looks like: https://www.dropbox.com/s/817f0jxvmjcgimh/file-input.png?dl=0

And this is the relevant html rendered by as_bootstrap filter:

<form enctype="multipart/form-data" action="" method="post" class="form-vertical">
  <div id="div_id_picture" class="form-group  ">
    <label for="id_picture" class="control-label  ">Picture</label>
    <div class="">
      <input class=" form-control" id="id_picture" name="picture" type="file" />
    </div>      
  </div>
</form>

In fields.html you have the following for radioselect:

"if choice.0 == field.value " to see if a radio should be checked

However, the equality test only work properly when chioices.0 is a unicode (field.value always is). However choices.0 could be any python type since it comes from the choices field in the FormField. Therefore, none of the radios will get checked whenever its a non-unicode type, even if the underlying values are the same.

How I fixed it is by changing everything to string as follows. You might choose to do something else:

if choice.0|stringformat:"s" == field.value|stringformat:"s"

Cheers,
azarias

Originally opened by @bmihelac at pinax/pinax-theme-bootstrap#36

as_bootstrap templatefilter wraps fields in control-group and controls divs. This currently makes it impossible to apply form-inline class.

Exception Value:
context must be a dict rather than Context.

Is there a way to apply a col-mm-x class to form items?
As an example, I need to render two text fields in one line. So they both should be col-md-6.
Thanks.

I ran across the RadioSelect bug fixed in 48b966f, and see that the version number was bumped to 2.0.3.post2 after the fix was merged in.

Is there a chance that 2.0.3.post2 could be added to PyPi? I'm currently just pinning to ad7c426 and installing from GitHub. I've got several sites still using Bootstrap 2.x, so I can't jump to django-forms-bootstrap 3.x just yet.

Thanks!

Hello! I was having trouble rendering radio buttons using your bootstrap filter, and after some trial and error in field.html, I was able to update that template to handle radio buttons. The following update to this template solves this problem:

{% if field|css_class == "radioselect" %}
    <div class="{{ css_classes.wrap }}">
        {% include "bootstrap/_field_errors_block.html" %}
        {% for choice in field %}
            <div class="radio">
                <label>
                    <input type="radio" {% if choice.choice_value|stringformat:"s" == field.value|stringformat:"s" %}checked="checked" {% endif %} name="{{ field.html_name }}" id="id_{{ field.html_name }}_{{ forloop.counter }}" value="{{ choice.choice_value }}"> {{ choice.choice_label }}
                </label>
            </div>
        {% endfor %}
        {% include "bootstrap/_field_help_text.html" %}
    </div>
{% endif %}

The main change involved updating the array the for loop loops over from field.field.choices to simply field. From there, one can access the value and label with {{ choice.choice_value }} and {{ choice.choice_label }}. I'm, of course, not sure if this is the best way to update this filter, and I haven't attempted to implement any of the other css_classes in field.html.

I am getting the following error:

Template error

In template c:\users\wings\fg-env\lib\site-packages\django_forms_bootstrap\templates\bootstrap\field.html, error at line 8
Invalid filter: 'css_class'

1 {% load bootstrap_tags %}
2
3 {% if field.is_hidden %}
4 {{ field }}
5 {% else %}
6

Is there any possibility to adapt this commit to the version 2.0.3.post1 (with bootstrap v2) in order to upgrade a project to django 1.11 without upgrading bootstrap to v3 ??

Error reported by Django 3.5

django_forms_bootstrap/templatetags/bootstrap_tags.py:28: RemovedInDjango110Warning: render() must be called with a dict, not a Context