That sounds like a good idea, but I’m not sure how this would be implemented.
When signing up for a WordPress.com account, you have to accept our Terms of Service, and then click on a link in a confirmation email to confirm the account creation. How would you handle that during the registration on your self-hosted WordPress site?
Hi Jeremy Herve
Thanks a lot for replying.
The first criteria is whether we are going to do this as a “Stop Press” feature – that is, whether we have agreed to do it as quickly as possible 🙂
If YES, then everything else can be sorted out fast. First of all, this is optional feature – those who want to enable it via Jetpack, can enable it. Those who do not, just do not – no forcing!
Now to come to your question : the answer is really very simple
Add a small checkbox ( I prefer in ‘selected state’) below the form
– This will create an account on both abc.com and wordpress.com and I agree to the TOSs of abc.com & wordpress.com
Simple.
Just hyperlink to both the TOSs to abc.com and wordpress.com
Less than 1% users bother about TOS though companies have to bother for understandable reasons 🙂
If done, this will make the life much simpler for millions and can remove the hindrance to easy adoption of Jetpack. Thanks.
While the checkbox sounds easy enough, I’m not sure how it could work. Your registration process would also have to query WordPress.com to see if an account already exists for this email address. Your process would also have to trigger the confirmation email from WordPress.com.
We currently do not have any process in place that allows you to create WordPress.com accounts from a third-party service, mostly for the reasons I listed above.
It could be something we add to Jetpack’s Single Sign On module in the future, but I’m afraid I can’t give you an ETA at the moment.
Querying wordpress.com can take place in the background and if email/username exists the same can be denied for new registration in the frontend.
As per the confirmation email, wordpress.com can authenticate valid and participating sites to have their own authentication. You can look at the ‘Drupal’ module of Drupal version 5
Nothing is impossible in the coding world. Question is : how much interested we are in such a solution 🙂 Often demand may not be there but once implemented people crazily use it. That is foresight like Apple 😉
Thanks for your feedback.
Nothing is impossible in the coding world. Question is : how much interested we are in such a solution 🙂 Often demand may not be there but once implemented people crazily use it. That is foresight like Apple 😉
I think we’re likely to improve the SSO module in the future to include WordPress.com registration, but I won’t be able to give you an ETA, as it’s not on our roadmap at the moment.
I took note of it though, so that’s something we’ll consider next time we work on SSO.
