In that case you should post up the relevant model, view, and form code. You may not be instantiating the form correctly.
Are you manually rendering it? -James On May 23, 2015 1:57 PM, "gabn88" <[email protected]> wrote: > Thank you for your reply! > > I have done the following steps: > 1. disable memcached -> Nothing changed > 2. Checked the databased -> Saved correctly > 3. Checked browser cache -> Used chrome dev mode (with disable cache) -> > Not working > > I'm really banging my head off on this one...:( > > > Op zaterdag 23 mei 2015 11:42:13 UTC+2 schreef James Schneider: >> >> Caching is often the culprit in these situations. Disable it and recheck. >> Obviously clear cookies and history in the browser as well. >> >> Also, verify that your database shows the correct data state (meaning >> that the fields in the database show as checked) once the models are saved, >> either through the Django shell or directly interrogating the database. >> >> Your web server process is least likely to be the culprit, unless it is >> telling the browser to use the cached version of your page for some reason. >> >> -James >> On May 23, 2015 12:26 AM, "gabn88" <[email protected]> wrote: >> >>> I have a MultipleSelectbox form that creates multiple select boxes >>> (wow!). >>> >>> Now, I use a model to save the selected values to, and also to *retrieve >>> the values back from*. >>> >>> If a user wants to update the model, I would like to show them which >>> checkboxes are checked already from the model. This works perfectly fine on >>> my dev server, but not on my production server and I can't seem to find the >>> issue. >>> >>> Could the reason be: 1. the memcached, 2. the mysql vs sqlite, 3. the >>> apache/wsgi/ngix vs. dev server configuration? >>> >>> I really don't know where to start searching. >>> >>> Thank you! >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Django users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> To post to this group, send email to [email protected]. >>> Visit this group at http://groups.google.com/group/django-users. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/django-users/5e28d66a-58a2-4f66-b77e-1a0898ae45b2%40googlegroups.com >>> <https://groups.google.com/d/msgid/django-users/5e28d66a-58a2-4f66-b77e-1a0898ae45b2%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/django-users. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-users/3bbdba86-5e05-4c5d-9c24-be48d324f377%40googlegroups.com > <https://groups.google.com/d/msgid/django-users/3bbdba86-5e05-4c5d-9c24-be48d324f377%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CA%2Be%2BciVGDET9Jo_OXLXk3ph8ZK9Y1gGF%2B8thsJ5DB-1fqc6HzA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
