Sorry for the delay. We're looking into the issue. The problem looks to be an issue with how the password is automatically generated and how EasySocial expects the password to be populated during registration. Since we're skipping large chunks of the EasySocial code and registration flow when a user is automatically registered, I'm not sure we'll be able to properly populate this so EasySocial knows the random password we generated.
The same issue is present with the user's avatar. Since it's not being set during the EasySocial registration process, they can't 'see' it when they try to send off their emails.
We will be testing further to see if there's a way that we can get around this and prepopulate the information in a way that EasySocial can see it, but I'm not sure that will be possible without some changes in EasySocial itself. We've already contacted them about a few things we'd love to see changed in their registration process to make our integration easier that will hopefully be available in their next big release.
I'll keep you posted on what we find. Unfortunately, the only suggestions I have for now are:
1) Don't user the Automatic Registration process and instead use the EasySocial registration flow. The user will still have a reduced registration flow, and the email will be correct.
2) Disable the sending of the password in the new user email. This is recommended from a security standpoint as well since the user will likely be logging in using their social network anyway. They'll also be able to update their password or use the Forgot Password feature should they need to login using Joomla.
We'll keep you posted on what we find, but I'm not exactly sure when we'll have an answer to this.
Thanks,
Alex
Generate Random Password
