Hi, Not sure what the problem is, maybe I expect too much. Set up amember and SMF. Got the Update database working in amember so that amember members show up in SMF after an Update DB in amember. I can kill all browsers, reopen a browser, go to the site, log into amember as a ordinary user with a valid subscription, then go to the unprotected directory where I installed SMF. and SMF sees me as a guest. I thought it would immediately recognize me as a logged in member and I would be logged into SMF. What is expected behavior here? I have done everything I can think of to setup the plugins in amember. Assigned membergroups in SMF ( guest(default), Player1, Player2 , etc). And assigned SMF membergroups to each product in amember. Thanks, John
If you are using the latest SMF 1.1.4 forums then you have to make sure you are using the latest amember SMF plug-in. Different versions of SMF handle cookies differently. The cookies contain credentials for logging in. If the Amember SMF plug-in does not allow you to configure the cookie name then you have an old version of plugin that will probably not work with 1.1.4 of SMF. Do a support ticket and they will provide you with right plug-in. I have amember and SMF integration with 1.1.4 and single sign on works. Jimmy
Hmmmm. It is frustrating to purchase the SMF plugin, discover it has no version information or documentation and waste many hours trying to get it to work only to learn that I apparently have an out of date version of the plugin. I lodged a support ticket 2 days ago and I'm still waiting. Sigh...