nathan rambeck

Note: This page last updated May 5, 2010. We are aiming at May 8 to release the next version (1.3). See the issue queue for info on the progress of specific features.

The RPX Drupal module began development in May 2009 and had it's first full release version on Jan. 8, 2010. Development is ongoing and the following roadmap is provided to communicate the completed and upcoming features for the module.

Initial Core Functionality

The RPX service allows website users to register or login to a site using their logins for popular 3rd party services such Facebook, Twitter and Google. The early beta versions of the module implemented this simple feature by exposing the RPX widget on login forms so Drupal users could login or register for a site with just 1 or 2 clicks.

Version 1.2

Version 1.0 and 1.1 got skipped because of some CVS tagging mistakes so 1.2 became the version of the first stable release.

• Add social publish features of the RPX service (paid accounts only)
• Add support for editing profile fields returned by an RPX provider

Version 1.3

The 2 primary goals of this version are to allow existing Drupal accounts to add an RPX identity and to provide mapping of profile fields provided by RPX to existing profile fields in Drupal.

• Allow RPX identities to be added to existing Drupal accounts
• Allow multiple RPX identities to be added a single Drupal account
• Allow identities to be removed from a Drupal account
• Allow RPX profile fields to be mapped to Profile module fields
• Allow RPX provider's profile image to be used as the Drupal profile image

Drupal 7

I'd like to start working on a Drupal 7 version of the module once v1.3 is complete.

Unschedule Features

• Provide documentation and/or functionality to map RPX profile fields to CCK fields used with modules like Content Profile