Apparently 6.x-1.0-beta10 isn't on the project page, but it was showing up on my drupal module updates page. Therefore, I went ahead and updated.
Based on the changelog here: http://drupal.org/node/667308 many of the issues are supposed to be 'fixed' but I found that almost all of them aren't (for me).
1) "Gigya Module is now independent on the profile module - fixing the bug noted http://drupal.org/node/655684."
This is fixed (profile module not needed), but if you do have profile module enabled and don't have any profile fields, then e-mail address and username fields won't show on registration form. Definitely a more minor bug than before.
2) "The module now correctly calls unlink to avoid the issues mentioned http://drupal.org/node/650322."
I think this is only semi-fixed. If you try to login and create a new user using social networks, but don't actually finish the process and register on drupal, you won't be able to connect an already made account to one that you attempted (but never finished) creating. If I login with facebook, but don't register. It won't let me go into an account I already have and link it to my facebook through "Social Network Connections" UI since it thinks the facebook account is already registered on the site. Therefore, it should not link to unless registration is completed.
3) THE MOST MAJOR ISSUE -" We have fixed several issues with the registration form. Bugs such as this one (http://drupal.org/node/647334) should be gone.
This one doesn't seem to be changed at all for me. Registration still ignores the location, captcha and other registration fields that aren't standard but are on the registration page. Out of all the issues, I think this one is still top priority since site registration is can really make or break a site.
I hope this helps. I just want to give some feedback. Considering beta10 isn't on the project page yet, maybe I'm using a version that isn't complete?
Comments
Comment #1
rfayThe problem with beta10 not showing on the project page is a Drupal.org infrastructure issue, and has nothing to do with this release. It's just a bug in d.o. #649254: version_extra can't just be string sorted. So your review is valid as is.
Comment #2
azinck commented#1 and #3 are hopefully now fixed by the patch I posted here: http://drupal.org/node/647334
#2 is honestly something I never noticed until you mentioned it. I'm not sure it can be fixed without Gigya altering their API. As soon as you log into Gigya via a social network Gigya considers you a "site user"; even if you don't complete the Drupal registration, and even though the Drupal site never called socialize.linkAccounts() or socialize.notifyLogin(). The only way to "free up" that social network account would be to call socialize.unlinkAccounts() but it's going to be tricky to do that reliably along every possible registration exit path.
Comment #3
azinck commentedI've opened a new issue for complaint #2 so that progress on it can be more easily tracked:
#678576: unlinkAccounts() must be called when a user logs into Gigya but doesn't complete Drupal registration
Comment #4
azinck commentedclosing...