Week 8 is over and we are just one month away from Google Summer of Code final evaluation. I mentioned in my last weekly summary that I would work on documentation about implementing a Social Auth integration. I started doing so, but in our last meeting Mateu, one of my mentors, suggested to start working on an implementer for Social Post.
Series on Social Auth implementer.
This week, I created the first two posts in the series for creating a Social Auth implementer. This real-life example is based on the Social Auth Google code. In these posts, I described how to define the implementer's dependencies in the info.yml and composer.json files and I described the Settings manager class.
This series will be updated in coming weeks. You can take at look at it now at http://blog.gvsanz.net/tag/social-api. I will also create a repository with comprehensibly documented code, so you can choose which approach suits you better to understand the code.
Social Post implementer.
As I mentioned above, one of the mentors asked me to begin working on a implementer for Social Post. Thus, we decided to work on one for Twitter. I might admit, it has been quite challenging so far; nonetheless, I have been able to move forward thanks to my mentors' support.
As of current, Social Post Twitter would allow site builders to give (drupal) permissions to specific roles. This permissions will allow users with the right role to grant (twitter) permissions to the site in order to tweet on their behalf.
To autotweet, the site should store an
oauth_token and an
oauth_token_secret, which are provided by twitter when the user grants permissions. These values should be stored in the database, therefore, I was working on creating a Twitter user entity.
This module is still in development. These are screenshots of how it looks so far.
There is not any content for this entity as I have not worked on the Twitter authentication yet.
For next week, I will continue working on the Social Post implementer named Social Post Twitter. I would like to say I will finish it by then, but I will probably not be able to accomplish this. This implementer requires a little more work than any of the ones I worked before. Nevertheless, I will try to have an immature version for next week.
As always, feel free to contact me if you have any question. You can also collaborate with the Social Initiative projects (social_api, social_auth, social_post, and social_widgets). We also have our weekly meetings, so follow the Social Initiative and join us on Wednesdays.
Stay tuned for the next weekly summary!