From 7721d6aeb5ca58d6ff321a4ce6a1c6c4ef975f6a Mon Sep 17 00:00:00 2001 From: Jonathan Liuti Date: Thu, 24 Apr 2014 11:24:31 +0200 Subject: [PATCH] Documentation improvement. I have just been bitten by this. While it's really related to select2, due to the fact that django-select2 adds his bits of abstraction on top of select2, I wasted quite some time making sure nothing was wrong with django-select2 in the first place... Hope it can help others, or help me if I happen to forget about it ;) --- django_select2/widgets.py | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/django_select2/widgets.py b/django_select2/widgets.py index d888080..b63ece4 100644 --- a/django_select2/widgets.py +++ b/django_select2/widgets.py @@ -127,6 +127,12 @@ class Select2Mixin(object): There are other such intricacies, based on which some options are removed. By enforcing this restriction we make sure to not break the code by passing some wrong concotion of options. + + .. tip:: According to the select2 documentation, in order to get the ``placeholder`` and ``allowClear`` + settings working, you have to specify an empty ```` as the first entry in your + ``