I'm working on two sites where one site is a public site and the 2nd site is the paid membership site. Each has its own domain name. They are both on the same server and host (Host Gator). One is the primary domain and the 2nd is an addon domain. We would like to use aMember to handle the signup, membership management and access to the paid membership site. Can aMember handle this? Which domain should aMember be installed in? Thanks, Mike
Can you provide more specifics? What is the role of the public site in this setup? If none, then this is no problem, you should install aMember on the 2nd site.. aMember does not care whether it is an addon domain or not.
The role of the public site is to sell visitors on buying a subscription membership to the private site. It makes sense that aMember would reside in the the private (protected) site. Thanks, Mike
aMember would be in the public directory- so people can login, order etc.. The content would go in a protected (private) directory. David
Okay, now I'm confused (a not uncommon condition for me). The public (sales) site is in one domain. (www.mysalessite.com) The private (membership) site is in another domain. (www.mymembershipsite.com) Will this setup work with aMember? Where does aMember need to be to be able to sign people up, process payment via 3rd party processor and grant/control access? Thanks, Mike
There are at least two possible scenarios: 1) people signup and login via amember that's installed in public section of public site. protection of content goes via remote_access plugin OR a plugin like Ken Gary's amProtect. 2) people signup via a custom sales page on public site - amember however is installed in public section of private site. Protection of private site content is done by amember. It's just a matter of what has your preference. Your customers will need to be aware of that your sending them from a to b (and tell them later where to find the content) or from b to a (and tell them that they'll be billed from a different domain).
Good points. I just want to set up aMember so that everything will work well and provide good protection for the membership site.
Well, with what you want it's not a matter if aMember will do it's job, that's a no-brainer aMember will do it's job... if properly configured