Roadmap / Planned features
April 2nd, 2015 by andre

Configuration to OAuth class

Admin pages regesign: depends on:
          Configuration to OAuth class

E-mail user on sign up

OAuth::process() sync with examples, better error handling

OAuth::process() add scope parameter for API suuport

External only login/signup support. depends on:
          Page merge

Page merge (almost done)

Page merge, migration options

Auto generate page on fresh install

Code split up into separate plugins, depends on:
          external: TGM plugin activation
                    where will the dependencies be located? ( / / bundled)

Recovery when external site fails

Widget support

Login form integration

Auto sign up: depends on:
         Fetch data from service
         Configurable required fields
--> global, per service?         

Fetch data from service: depends on
         API support
         Configurable required fields

API support: depends on: 
          Configuration to OAuth class
          OAuth::process() to use tokens stored in database. 
          add token_secret to database to support OAuth 1.x APIs

Alternative OAuth user identification: Depends on: 
          API Support
Currently the token received from the OAuth server is used as a key to identify the user. This works for most services (Facebook, Google, Twitter, github.....) but there appear to be some services that give a different token each time the user authenticates. For these cases, the solution is to retrieve an unique key for the using from the service, using an API call.

WooCommerce integration

Leave a Reply

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>
»  Substance:WordPress   »  Style:Ahren Ahimsa