Deprecate RCP

[spencerfinnell]

Less plugin-specific and more about our general setup. RCP won't be necessary anymore unless we want to still offer VIP support.

Thoughts @adampickering

[adampickering]

I like that RCP sends out emails telling customers that their support is about to expire, also from what I believe the terms of support service on Envato are that we are not allow to sell our own support packages on our own site. We need to remove VIP all together.

[spencerfinnell]

Well now we'll hope Envato will send out those emails since the subscription is managed through them now.

[spencerfinnell]

We just need a simple registration form now; or we can use the default wp-login.php?action=register to register as a standard Subscriber.

[adampickering]

When we use the oAuth login process with Envato can we not send that user data back to our WordPress install to create an account on our system?

[spencerfinnell]

Yeah that makes sense. The API doesn't return user info by default, but we can request it I think.

[adampickering]

We need to gather as much user data as possible when they perform the oAuth connection process on our site, would be very useful to have fields the users admin area that shows purchase keys and envato usernames, but i guess it will already show their envato username as that is what will be used. I think the issue might be when we switch over to the new system as usernames customers have previously used will match their new account using the oAuth process.

[spencerfinnell]

Yeah which is why I had them registering first. Just create a standard user in WordPress like normal then link that user account to an Envato account with oAuth.

Since we have existing users we can't really register new users because we already have so many people with accounts. So it will probably need to stay that way.

[spencerfinnell]

This is the only info we can get: https://build.envato.com/api/#market_Account