If you're running amember on two sites, you can't really use the remote plugin. (According to support). So why bother with it? Why not just code a form that takes in the username and password and then checks if it's active or not. If active and not present in the second sites db, just add the info to it. Let them in and bob's your uncle. Seems like a simpler solution then a plugin that only works when one site is not running amember. (Which is odd to set it up that way as you'd think all the membership sites would be running amember with their own install?) Anyway, am I overlooking something here? Is there a way to do it with amember remote that I'm not aware of? Any input is appreciated.
I assume the idea behind the aMember Remote plugin is to run multiple sites with a single installation of aMember. The problem with creating a form the way you describe is making sure the communication between the form and aMember is secure and not vulnerable to hacking.
Good point. After getting the remote one to work, (it does work perfectly), I ran into issues with my other scripts. Specifically vbulletin. Amember remote is not designed to work with your other plugins, (and they never said it was), but people would login fine, but then have to create their own vbulletin account when using amember remote. The solution for me is to write a script that adds them as a member to the other site via curl and some php. (Using the amember admin form for add user to do so), then adding a free signup subscription, then checking once per day to see if they cancelled their original subscription or not via cron. It's an "involved" solution, but that way they get their info added to vbulletin and all my other plugins too. I haven't written this yet, but will do so or get someone to do it for me.
I think that vbulletin doesn't work because of the cookies as they are probably not on the same domain? Cross-domain cookies is a problem in general.
You can do this more simple way. Just create a copy of your vBulletin plugin (so you will be able to enable two plugins in aMember CP) and configure second plugin to work with database on different domain(of course if that database allow external connections) However as mentioned by erwinvdb single login will not work because domains will be different.
I've got it working, I have amember installations on two different domains which reside on two different servers. Now members of site1.com can login to site2.com AND site2.com's vbulletin without any issue. The only problem I'm having now is when the database is being rebuilt, I'm losing admin status in vbulletin. It's got to be something minor I'm overlooking.
vBulletin plugin. you might have to edit that plugin to remove the limitation that prevents it from showing "Administrator" group in the config tab, and then select the Admin group as one of the groups not to be affected/touched. That might help.