No, the cache was off all the time.
On Oct 19, 8:44 am, web-junkie <[EMAIL PROTECTED]> wrote:
> Did you activate the cache in Django? I once discovered an issue with
> that..
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Did you activate the cache in Django? I once discovered an issue with
that..
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
T
I got the same problem
2007/10/18, Jarek Zgoda <[EMAIL PROTECTED]>:
>
>
> Robert Šmol napisał(a):
>
> > I have HomePage with login bar with a form for user to log in. I use
> > django.contrib.auth.login to log user in. When I enter it from the
> > /accounts/login/ page it works ok. However try
Robert Šmol napisał(a):
> I have HomePage with login bar with a form for user to log in. I use
> django.contrib.auth.login to log user in. When I enter it from the
> /accounts/login/ page it works ok. However trying to login from homepage
> is not working. I have to do it twice (always). On djang
Hi Robert,
I had the same problem. Since I switched from FCGI to mod_python the
problem disappeared. I still don't know what was the _real_ reason for
that. However, I noticed it was possible to get rid of the problem
temporarily by clearing the browser cache (or cookies). I bet it was
caused by
Hello,
I have HomePage with login bar with a form for user to log in. I use
django.contrib.auth.login to log user in. When I enter it from the
/accounts/login/ page it works ok. However trying to login from homepage is
not working. I have to do it twice (always). On django# there were more
users wi
6 matches
Mail list logo