Grokbase › Groups › Django › django-users › April 2013
FAQ
Hi, I just pip installed django-social-auth from omab today on
github(beginner here). I think I can almost get it to work with facebook
login, but I always have this "InternalError: Exception Value: current
transaction is aborted, commands ignored until end of transaction block",
after I log in with my facebook account and before I redirect to the
profile page. The request url shows
http://127.0.0.1:8000/complete/facebook/?redirect_state=xxx&code=xxx&state=xxx.
I'm using Django 1.5. Can anybody give me some directions to debug this?

Thank you tons,
Jeff


--
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Search Discussions

  • Brad Pitcher at Apr 15, 2013 at 3:57 pm ⇧
    In my experience, that particular error always means that the database
    doesn't match what you have in your models. Try a syncdb and/or check your
    south migrations to make sure your database is up to date.

    ---------
    Brad Pitcher
    Software Developer
    (702)723-8255

    On Sun, Apr 14, 2013 at 11:01 PM, Jeff Hsu wrote:

    Hi, I just pip installed django-social-auth from omab today on
    github(beginner here). I think I can almost get it to work with facebook
    login, but I always have this "InternalError: Exception Value: current
    transaction is aborted, commands ignored until end of transaction block",
    after I log in with my facebook account and before I redirect to the
    profile page. The request url shows

    http://127.0.0.1:8000/complete/facebook/?redirect_state=xxx&code=xxx&state=xxx.
    I'm using Django 1.5. Can anybody give me some directions to debug this?

    Thank you tons,
    Jeff


    --
    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?hl=en.
    For more options, visit https://groups.google.com/groups/opt_out.

    --
    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?hl=en.
    For more options, visit https://groups.google.com/groups/opt_out.
  • Jeff Hsu at Apr 15, 2013 at 4:26 pm ⇧
    Thanks for the reply. I did sync db before I run the code. I am actually
    on localhost when I test it. Do I have to be online to test it? But, I
    was successful on authenticating in the Login Dialog. This error happens
    during the code exchanging process for the access token I think.

    Thanks,
    Jeff

    On Mon, Apr 15, 2013 at 8:49 AM, Brad Pitcher wrote:

    In my experience, that particular error always means that the database
    doesn't match what you have in your models. Try a syncdb and/or check your
    south migrations to make sure your database is up to date.

    ---------
    Brad Pitcher
    Software Developer
    (702)723-8255

    On Sun, Apr 14, 2013 at 11:01 PM, Jeff Hsu wrote:

    Hi, I just pip installed django-social-auth from omab today on
    github(beginner here). I think I can almost get it to work with facebook
    login, but I always have this "InternalError: Exception Value: current
    transaction is aborted, commands ignored until end of transaction block",
    after I log in with my facebook account and before I redirect to the
    profile page. The request url shows

    http://127.0.0.1:8000/complete/facebook/?redirect_state=xxx&code=xxx&state=xxx.
    I'm using Django 1.5. Can anybody give me some directions to debug this?

    Thank you tons,
    Jeff


    --
    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?hl=en.
    For more options, visit https://groups.google.com/groups/opt_out.

    --
    You received this message because you are subscribed to a topic in the
    Google Groups "Django users" group.
    To unsubscribe from this topic, visit
    https://groups.google.com/d/topic/django-users/9YkrCD2veRQ/unsubscribe?hl=en
    .
    To unsubscribe from this group and all its topics, 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?hl=en.
    For more options, visit https://groups.google.com/groups/opt_out.

    --
    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?hl=en.
    For more options, visit https://groups.google.com/groups/opt_out.
  • Serdar Dalgic at Apr 15, 2013 at 5:28 pm ⇧
    Hi,
    On Mon, Apr 15, 2013 at 9:01 AM, Jeff Hsu wrote:

    Hi, I just pip installed django-social-auth from omab today on
    github(beginner here). I think I can almost get it to work with facebook
    login, but I always have this "InternalError: Exception Value: current
    transaction is aborted, commands ignored until end of transaction block",
    after I log in with my facebook account and before I redirect to the
    profile page. The request url shows

    http://127.0.0.1:8000/complete/facebook/?redirect_state=xxx&code=xxx&state=xxx.
    I'm using Django 1.5. Can anybody give me some directions to debug this?
    Your question is Django-Social-Auth specific. If you ask that question
    http://groups.google.com/group/django-social-auth you would get more
    accurate and fast answer. I'd suggest you to do so.

    I've met the same error while using postgresql as the database, and the
    reason was that, when a transaction meets an error, it changes its
    stabilized state. If you do not rollback this transaction, further
    transactions after this one gives such error. You should find the
    problematic transaction to get rid of this error. For details, see
    https://docs.djangoproject.com/en/dev/topics/db/transactions/#handling-exceptions-within-postgresql-transactions

    More info about this issue from Django Social Auth users/developers would
    appear on Django Social Auth mailing list.

    --
    - Serdar Dalgıç <[email protected]>
    FLOSS Developer, Life & Nature Hacker
    twitter: https://twitter.com/serdaroncode

    --
    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?hl=en.
    For more options, visit https://groups.google.com/groups/opt_out.
  • Jeff Hsu at Apr 15, 2013 at 5:50 pm ⇧
    Hello Serdar,

    Thank you so much, I do use postgresql as my database. The problem
    might be what you listed above, I'll take deep look at it. If I have more
    questions, I'll post it in that group. Thank you!

    Jeff

    On Mon, Apr 15, 2013 at 1:36 AM, Serdar Dalgic wrote:

    Hi,
    On Mon, Apr 15, 2013 at 9:01 AM, Jeff Hsu wrote:

    Hi, I just pip installed django-social-auth from omab today on
    github(beginner here). I think I can almost get it to work with facebook
    login, but I always have this "InternalError: Exception Value: current
    transaction is aborted, commands ignored until end of transaction block",
    after I log in with my facebook account and before I redirect to the
    profile page. The request url shows

    http://127.0.0.1:8000/complete/facebook/?redirect_state=xxx&code=xxx&state=xxx.
    I'm using Django 1.5. Can anybody give me some directions to debug this?
    Your question is Django-Social-Auth specific. If you ask that question
    http://groups.google.com/group/django-social-auth you would get more
    accurate and fast answer. I'd suggest you to do so.

    I've met the same error while using postgresql as the database, and the
    reason was that, when a transaction meets an error, it changes its
    stabilized state. If you do not rollback this transaction, further
    transactions after this one gives such error. You should find the
    problematic transaction to get rid of this error. For details, see
    https://docs.djangoproject.com/en/dev/topics/db/transactions/#handling-exceptions-within-postgresql-transactions

    More info about this issue from Django Social Auth users/developers would
    appear on Django Social Auth mailing list.

    --
    - Serdar Dalgıç <[email protected]>
    FLOSS Developer, Life & Nature Hacker
    twitter: https://twitter.com/serdaroncode

    --
    You received this message because you are subscribed to a topic in the
    Google Groups "Django users" group.
    To unsubscribe from this topic, visit
    https://groups.google.com/d/topic/django-users/9YkrCD2veRQ/unsubscribe?hl=en
    .
    To unsubscribe from this group and all its topics, 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?hl=en.
    For more options, visit https://groups.google.com/groups/opt_out.

    --
    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?hl=en.
    For more options, visit https://groups.google.com/groups/opt_out.
  • Jeff Hsu at Apr 15, 2013 at 10:39 pm ⇧
    I solved the problem. The problem is that I set up my project with south.
    So, I have to use south migration to set up the proper database schema for
    social_auth.

    Thanks,
    Jeff

    On Mon, Apr 15, 2013 at 10:50 AM, Jeff Hsu wrote:

    Hello Serdar,

    Thank you so much, I do use postgresql as my database. The problem
    might be what you listed above, I'll take deep look at it. If I have more
    questions, I'll post it in that group. Thank you!

    Jeff

    On Mon, Apr 15, 2013 at 1:36 AM, Serdar Dalgic wrote:

    Hi,
    On Mon, Apr 15, 2013 at 9:01 AM, Jeff Hsu wrote:

    Hi, I just pip installed django-social-auth from omab today on
    github(beginner here). I think I can almost get it to work with facebook
    login, but I always have this "InternalError: Exception Value: current
    transaction is aborted, commands ignored until end of transaction block",
    after I log in with my facebook account and before I redirect to the
    profile page. The request url shows

    http://127.0.0.1:8000/complete/facebook/?redirect_state=xxx&code=xxx&state=xxx.
    I'm using Django 1.5. Can anybody give me some directions to debug this?
    Your question is Django-Social-Auth specific. If you ask that question
    http://groups.google.com/group/django-social-auth you would get more
    accurate and fast answer. I'd suggest you to do so.

    I've met the same error while using postgresql as the database, and the
    reason was that, when a transaction meets an error, it changes its
    stabilized state. If you do not rollback this transaction, further
    transactions after this one gives such error. You should find the
    problematic transaction to get rid of this error. For details, see
    https://docs.djangoproject.com/en/dev/topics/db/transactions/#handling-exceptions-within-postgresql-transactions

    More info about this issue from Django Social Auth users/developers would
    appear on Django Social Auth mailing list.

    --
    - Serdar Dalgıç <[email protected]>
    FLOSS Developer, Life & Nature Hacker
    twitter: https://twitter.com/serdaroncode

    --
    You received this message because you are subscribed to a topic in the
    Google Groups "Django users" group.
    To unsubscribe from this topic, visit
    https://groups.google.com/d/topic/django-users/9YkrCD2veRQ/unsubscribe?hl=en
    .
    To unsubscribe from this group and all its topics, 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?hl=en.
    For more options, visit https://groups.google.com/groups/opt_out.

    --
    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?hl=en.
    For more options, visit https://groups.google.com/groups/opt_out.
  • Alex Ksenzov at Apr 16, 2013 at 3:40 pm ⇧

    Hi Jeff .I have this problem too, but still can't figure out. Can you
    please provide resolving more detail and step by step please. Thanks.
    --
    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?hl=en.
    For more options, visit https://groups.google.com/groups/opt_out.
  • Jeff Hsu at Apr 16, 2013 at 3:58 pm ⇧
    First, check to see if you have 3 tables, social_auth_association,
    social_auth_nonce, and social_auth_usersocialauth. If not, you need to
    create those DB tables. SyncDB did not work for me. I had south
    installed. So, you just do use south to create proper schema for those DB
    tables. Some tutorial on south:
    http://south.readthedocs.org/en/latest/tutorial/part1.html

    Jeff

    On Tue, Apr 16, 2013 at 8:35 AM, Alex Ksenzov wrote:

    Hi Jeff .I have this problem too, but still can't figure out. Can you
    please provide resolving more detail and step by step please. Thanks.

    --
    You received this message because you are subscribed to a topic in the
    Google Groups "Django users" group.
    To unsubscribe from this topic, visit
    https://groups.google.com/d/topic/django-users/9YkrCD2veRQ/unsubscribe?hl=en
    .
    To unsubscribe from this group and all its topics, 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?hl=en.
    For more options, visit https://groups.google.com/groups/opt_out.

    --
    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?hl=en.
    For more options, visit https://groups.google.com/groups/opt_out.
  • Rainy at Apr 17, 2013 at 2:51 pm ⇧
    When you get this error, you need to look at your database error log, e.g.
    for postgres 8.4 on linux:

    tail -n100 /var/log/postgresql-8.4-main.log

    It should tell you the exact sql command that caused the first error (you
    might need to scroll up).


    On Monday, April 15, 2013 2:01:21 AM UTC-4, Jeff Hsu wrote:

    Hi, I just pip installed django-social-auth from omab today on
    github(beginner here). I think I can almost get it to work with facebook
    login, but I always have this "InternalError: Exception Value: current
    transaction is aborted, commands ignored until end of transaction block",
    after I log in with my facebook account and before I redirect to the
    profile page. The request url shows

    http://127.0.0.1:8000/complete/facebook/?redirect_state=xxx&code=xxx&state=xxx.
    I'm using Django 1.5. Can anybody give me some directions to debug this?

    Thank you tons,
    Jeff

    --
    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?hl=en.
    For more options, visit https://groups.google.com/groups/opt_out.

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupdjango-users @
categoriesdjango, python
postedApr 15, '13 at 6:01a
activeApr 17, '13 at 2:51p
posts9
users5
websitedjangoproject.com

5 users in discussion

Jeff Hsu: 5 posts Brad Pitcher: 1 post Serdar Dalgic: 1 post Alex Ksenzov: 1 post Rainy: 1 post

Content

People

Support

Translate

site design / logo © 2023 Grokbase