From my experience with this integration I can say that the aMember/WordPress registration/login sync works well. I really can't think of a time I have seen this fail. Again, it is all about the sync between aMember and WordPress. BuddyPress allows WordPress users to join groups and the group access is handled like a subscription product from aMember. All registration and logins/logouts must be handled in aMember for this to work correctly. That is why you uncheck "Anyone can Register". This is covered on this page of the WordPress documentation. The reason BuddyPress "requires" that WordPress registration to be turned on is that BuddyPress is designed to handle registrations through the "Register" page. With the aMember integration you leave WordPress registration turned off and do not present the Register page to the user. The only issue with this is they don't see the extended profile page during the registration process, but that can be dealt with as a secondary action. From my testing last night, I am certain that BuddyPress protection is not working correctly. I sent in a report last night to Alexander and he has already responded. I actually have sent him two additional screen recordings this morning. Just a little more tweaking and this should be a done deal. I will place detailed documentation in the WordPress Installation Guide Wiki as soon as this gets ironed out.