Re: Multiple timezone support for datetime representation

> I'm going to use the same trick used by USE_L10N and explained by Anssi: set > USE_TZ to False in global_settings.py and to True in the template of > settings.py. This preserves backwards compatibility but the new code is the > default for new projects. This isn't gonna work because your new

Re: Multiple timezone support for datetime representation

Thanks Paul, Anssi, Mikhail and Daniel for reviewing the proposal! Here are some answers to your remarks. On 3 sept. 2011, at 20:19, Paul McMillan wrote: > My main concern with your proposal is that it may require two > different code paths for a lot of code. Currently, my best guess is:

Re: CSRF verification failed. Request aborted.

i think this will help: https://docs.djangoproject.com/en/dev/ref/contrib/csrf/#how-to-use-it allink.creative Die interdisziplinäre und marktnahe Designagentur.

Re: CSRF verification failed. Request aborted.

Please ask questions about using Django on the django-users mailing list. The topic of this list is the development of Django itself. Karen -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to

CSRF verification failed. Request aborted.

wassup people, am learning django by doing a small app but my form gives this error "CSRF verification failed. Request aborted." when i click the submit button. i've to read about CSRF but i dont it get quite clearly. please help -- You received this message because you are subscribed to the

Re: Suppressed template errors in admin

Am 25.08.2011 06:19, schrieb h3: But this would have side effects on the non-admin templates too.. so it's not ideal. Maybe something like this: TEMPLATE_STRING_IF_INVALID = {'default: '!! Invalid var !!', 'django.contrib.admin': ''} I do a hack in my admin.py:

Re: Suppressed template errors in admin

On 6 Sep., 09:17, Thomas Guettler wrote: > Ole, can you please set up a a branch at github or bitbucket? Eh, is that not overkill? I don't think discussing this is worth anyone's time. No need to promise anything or elevate this to a Big Decision as long as it's about trivial

.save_m2m() failing with multi-database error

I think I might have found an issue related to https://code.djangoproject.com/ticket/14849. The last comment says to please email the django-dev group if there are any questions about the ticket, so here I am. I've done my best to provide a complete test case. I have an Event model with

Re: Suppressed template errors in admin

On Tue, Sep 6, 2011 at 3:17 PM, Thomas Guettler wrote: > > > Am 03.09.2011 16:13, schrieb Luke Plant: >> On 25/08/11 00:39, Russell Keith-Magee wrote: >> >>> On principle, I have no objection to the idea of making the admin >>> templates more robust in the presence of