Files
2012-02-21 01:15:00 -05:00

1 line
1.3 KiB
JSON

[{"user_id": 44583, "stars": [], "topic_id": 48976, "date_created": 1325184114.4232769, "message": "I looked at the example app. The example/views.py seems to use the standard django auth interface (I'm assuming that django-social-app purposely plugs into django auth's interface so that this interface is preserved). In example/models.py shows the custom user and signals use.", "group_id": 5196, "id": 2748342}, {"user_id": 44583, "stars": [], "topic_id": 48976, "date_created": 1325184694.3234019, "message": "Those examples are great, but now I want to do something that I don't see in the example app. If I want to do something simple in my django view like get the user's facebook id, is the recommended way to do this: use the RequestContext(request)['social_auth'] to get the information or should i get access to social-auth's model info directly?", "group_id": 5196, "id": 2748351}, {"user_id": 20656, "stars": [{"date_created": 1325243715.0197899, "user_id": 44583}], "topic_id": 48976, "date_created": 1325187166.5996699, "message": "You can hook a custom function on the process pipeline (sorry no doc about it yet) that will retrieve your desired data. Also you can do user.social_auth.filter(provider='facebook') and use the access_token stored in extra_data to talk with Facebook API.", "group_id": 5196, "id": 2748362}]