Hi again Carl,
I was describing what would be the best case scenario from a UX standpoint. From my point of view at this time, I would be MORE than happy with the very sensible solution you outline in your last message's second paragraph: if users entered an existing email and other creds don't match, then show a validation message telling them the email is already used in the network and they need to use the same username and password in order to be added to the current site. An awesome bonus would be to offer to send the creds to the email address in the account if they forgot the un and pw but that is absolutely not necessary for me right now.
On the other hand, if they did enter an existing email (site x) when they're trying to register to site y AND they used the correct un and pw from site x then I'd simply register them to the new site no questions asked. If some admins would like to have an option to present the user with a message notifying them that they are already registered on site x and they just registered on site y then it might be a great nice-to-have for some but absolutely not needed in this case for me.
I get your point about networks where each site is completely separate and visitors should remain unaware that the site they are visiting is on a network with several sites in it. In my case, it's the opposite and it's clear the "sub-sites" are on a network with the main site and share branding and all that. All the sub sites have the same look and structure (pages) and only the main site is different (much larger in terms of pages, etc). It's a completely gut feeling guess on my part but I would bet my situation is much more common than networks of isolated sites. I mean, even on wordpress.com users know their blog is on that one huge network.
So, would this be doable for 1.0 (or 1.x.x update soon after) :
On registration attempt to site y from user with existing account on different site(s) on network, either of these two scenarios would be covered:
Case 1- If user used entered an existing account's email but supplied incorrect un and pw then notify user of duplicate email and tell them to enter correct un and pw from existing account (would be nice to tell them what site(s) the account is already registred to)
Case 2- If user used entered an existing account's email and supplied matching un and pw then simply register them to site y without further hassle to them (that is basically what I expected to happen as I had entered the correct un and pw)
Thanks again very much for your responsiveness! Have you got any feedback from your Twitter enquiry on this matter?
Posted 10 years ago on Wednesday February 16, 2011 | Permalink