Before I go down the path, I just want to know if I am trying to do too much. I want to use amember as the core user management of my site, but intend to incorporate several different packages for my members. Is there a limitation on how many different sign-on scripts I incorporate into amember? For example, I want to have the following packages incorporated into a single signon: wordpress for content, eFront for LMS, magento for shopping cart, trellis for help ticket, a job board (still looking for right solution), a forum package Am I crazy to try to incorporate that many different packages? I wonder if others use this many or more ?? Also, does it make a difference with the single signon if the packages are subdomains vs. subfolders? (i.e. wordpress.mysite.com vs. mysite.com/wordpress or shop.mysite.com vs mysite.com/shop ) Does that change if I put amembers as a subdomain (i.e. members.mysite.com vs. mysite.com/amembers ) Any foresight from those who have been down this path would be helpful to steer me before I have to learn any lessons the hard way. Im a developer so Im not afraid to roll up my sleeves if necessary, as long as I know it can work relatively cleanly. Thanks!
The number of add-ons you mention should offer not problem at all. When I am fiddling with plugins I sometimes have about 40 installed doing stuff. Larry
Ideally, it would be nice having a built-in feature to deactivate all plug-ins and reactivate all at once. WordPress does this nicely. Maybe aMember Team would put this on his next release.