On Oct 10, 12:02 pm, Robocop <[EMAIL PROTECTED]> wrote:
> Unfortunately, that is the explanation. I really appreciate all the
> help though; how disappointing that i didn't learn anything other than
> not allowing anyone to touch my projects without me around.
>
> On Oct 10, 9:59 am, "Karen
Unfortunately, that is the explanation. I really appreciate all the
help though; how disappointing that i didn't learn anything other than
not allowing anyone to touch my projects without me around.
On Oct 10, 9:59 am, "Karen Tracey" <[EMAIL PROTECTED]> wrote:
> On Fri, Oct 10, 2008 at 12:51
On Fri, Oct 10, 2008 at 12:51 PM, Robocop <[EMAIL PROTECTED]> wrote:
>
> Bad news guys, someone deactivated my test user and didn't tell me.
> I'm so sad.
>
Do you mean that is the explanation for why auth.login hasn't been working?
Or is there still a problem that needs to be investigated?
Bad news guys, someone deactivated my test user and didn't tell me.
I'm so sad.
--~--~-~--~~~---~--~~
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
Also worth noting: I tried using the built in
django.contrib.views.login, but that resulted in the same behavior.
Did some automagic default session setting in django .96 get changed
to something that needs to be manually set in 1.0?
--~--~-~--~~~---~--~~
You
Sorry for the sloppy post, i was reposting an old ignored thread in my
frustrated rage. The code i'm working with right now looks like:
from django.contrib import auth
def log(request):
news_list = New.objects.all().order_by('-date')
if request.method == 'POST':
username =
On Thu, Oct 9, 2008 at 5:18 PM, Robocop <[EMAIL PROTECTED]> wrote:
>
> Having looked through the archived posts, i found a similar problem
> that had found no solution:
> http://groups.google.com/group/django-users/browse_thread/thread/bf05...
>
I get a 'topic not found' error from Google Groups
On Thu, Oct 9, 2008 at 4:15 PM, Robocop <[EMAIL PROTECTED]> wrote:
>
>
> actually i read that wrong, i do not know what path it is being sent
> to.
I think that's the root path... you can verify in firefox if you look
under preferences > privacy > show cookies. You said you moved from a
dev
actually i read that wrong, i do not know what path it is being sent
to.
--~--~-~--~~~---~--~~
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
To
Cookie=sessionid=6bc37c43a444db3aaf60a5c61e85bb01; support_tabs=0
Content-Type=application/x-www-form-urlencoded
Content-Length=52
POSTDATA=username=moneybags=dollars=%2F=0=0
this is the relevant tamperdata output, though i'm not necessarily
sure how to check if the session cookie is being set
Cookie=sessionid=6bc37c43a444db3aaf60a5c61e85bb01; support_tabs=0
Content-Type=application/x-www-form-urlencoded
Content-Length=52
POSTDATA=username=moneybags=dollars=%2F=0=0
this is the relevant tamperdata output, though i'm not necessarily
sure how to check if the session cookie is being set
On Thu, Oct 9, 2008 at 3:25 PM, Robocop <[EMAIL PROTECTED]> wrote:
>
> All right, this is getting absolutely ridiculous. I tried to
> workaround my problems by using the built in contrib.auth.views.login,
> and of course this resulted in the same behavior. I am very reluctant
> to think this is
I'm going to burn my server down, i could really use some help.
--~--~-~--~~~---~--~~
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
To unsubscribe
All right, this is getting absolutely ridiculous. I tried to
workaround my problems by using the built in contrib.auth.views.login,
and of course this resulted in the same behavior. I am very reluctant
to think this is a bug, but rather some type of session
misunderstanding, but i'm running out
Having looked through the archived posts, i found a similar problem
that had found no solution:
http://groups.google.com/group/django-users/browse_thread/thread/bf05...
It looks like django is not actually logging my user in, or not
creating a session. I have a very simple snippet for login
15 matches
Mail list logo
