That's correct. Those are, unfortunately, issues with Joomla 3.2.0 that are being fixed. We *do* have fixes in JFBConnect for the non-activation case and other issues, which we could be worked around in our extension (without modifying core files).
For example, Joomla 3.2.0 will *always* re-hash a user's password when they login. Since a user logging in through a social network doesn't have a password, Joomla was creating a garbage password for the user. We work around that case through a few different code changes that are possible in our code.
We've also be working with the 3.2.1 patch release, and have provided feedback to the Joomla core team on what we've found and are patiently waiting for that release. Originally, it was announced that it would be available around November 27th. That, obviously, didn't happen. We're very hopeful that it will be released around mid-December now, and we are continuing to test with it to ensure that JFBConnect will work with the fixes and changes in that release.
I hope that helps explain. We wish the 3.2.0 release was a lot more solid and didn't have these password issues. They affect all extensions, not just JFBConnect. We have been doing what we can to usher the 3.2.1 release along with feedback and testing to the Joomla project.
If you have any other questions, feedback or suggestions, just let me know!
Thanks,
Alex
Issues with Joomla 3.2.0
