Thanks ,
Not trying to be contrary and I’m sorry for the snippy tone of my previous reply, I was a bit frustrated. But, I’ve been working with multisite on almost every project for nearly 3 years now. A pluging can be more aware of users on the network than you seem to think. Look at :
http://codex.wordpress.org/WPMU_Functions/get_blogs_of_user for starters which returns an array of all blogs a user belongs to.
Also see this for getting a user’s data from a particular site:
http://wordpress.stackexchange.com/questions/33456/get-user-meta-to-return-user-meta-only-for-current-blog-in-multi-site
This an other stuff I quickly researched yielded this hook that could be used to automatically copy Paypal info from the main subscription site to a sub site a user is being registered to:
http://codex.wordpress.org/Plugin_API/Action_Reference/user_register
First example on that page would be a base to get the PayPal data from the main site to the blog the user has just been registered to (by an admin in my case) but using update_user_option which can be blog specific instead update_user_meta which is global:
http://codex.wordpress.org/Function_Reference/update_user_option
I’m just a hack building sites for my clients but my basic use case seems entirely possible from the above after 10 minutes of research. I haven’t tested any of this obviously and I may just try to do it myself but I would think a powerful membership plugin like s2Member should have this built-in or maybe true a smaller plugin addon one could install on sub sites.
But, like I said, it seems the functionality and workflow s2Member caters for is different from this. The first reply you quoted above does not pertain to this situation at all. I knew s2Member would not enable me to automate site creation. The second reply goes right to the crux of things though but, from experience on muiltisite, it contains inncuracies. When Raam says:
“That means you cannot share users, logins, or other data across the sites”.
…that may be true for s2Memebr itself in its current state but that is certainly not because of limitations in WordPress itself as far as I can see (I may be wrong but the obove ressources and my own experience with MS would tell me otherwise). I run another multisite network with 83 sites on the network. Users can be part of several sites on it and, in this case, they have their own site and also belong to a support and the main site. Much like my current project except there’s no subscription mechanism on the site at all. Client prefers to do this all manually and separately still. But basic user meta is shared and there’s site specific user meta too including the user role which is different for each site a user belongs too on that 83 sites network.
Just food for thought. For now, I’ll be moving on with the project doing these things manually.
Thanks!