enable Gigya for comments

I need more information about what you mean regarding 'integrate GS with comments'... currently gigya can be used to publish notifications about comments, or allow users to update their status if they made a comment.

ahh, okay the original design was that gigya is to be used to 'comment' about content on drupal sites. Whether this be new nodes, users, or comments. (yes comments about comments ;-) )

In our 'expected' configuration, a site administrator would setup gigya to monitor people creating comments, and execute an action once that comment was made. That action could be a newsfeed for facebook (sending out newsfeed item that you just commented on some piece of content) or it can be a status update; If you create a comment, once you press submit, a popup would occur asking the user to update their status in regards to the comment they just made.

Comments themselves are tied to nodes. So for adding actions to comments, looking at the screenshot in #3, you'll create an action that is applicable to certain node types. Then you'd go over to the triggers section, and assign that action to a comment trigger.

From a fairly non-technical Drupal administrator standpoint, I think I understand where this feature request is coming from.

I have a Drupal site that I cannot decide which module to implement: Facebook Connect, Google Friend Connect, or Gigya Socialize. Of the 3, Gigya seems to be the most robust and maintained, but it lacks one key feature of the other 2: comment integration.

By comment integration, I mean capturing new users who are leaving comments and authenticate them via a social network (simultaneously syncing them with a new local Drupal user account), and pushing these comments to that social network. Comments are the place new visitors interact the most, so it makes sense to emphasize capturing them there as opposed to a user registration page (or block).

Google Friend Connect module does a great job of capturing users in the comment section, but it still has too many bugs, and it doesn't go any farther with it's purpose. Gigya Socialize module does a great job of extending social network actions and integrating them into Drupal for those who want to get really advanced, but it completely skips the basics of comment integration. Facebook Connect module would be perfect because adding social actions to a website based on only the main social network is more straightforward to a user, (and from a development standpoint), but it has some critical issues (confusing user interaction) that have not been fixed.

So what am I saying? Please put the multi-network registration capability into one button on the comments like Google Friend Connect! Or at least expand the vision of this module to include a type of simple comments integration for one or more social networks.

My only wish is that it's not a whole 'nother year before one of these Drupal/social network bridge modules is ironed out enough to finally install.

subscribing

Subscribing.

subscribing

It's been a while since any real discussion happened on this issue. What exactly are you guys looking for? You can currently use Gigya to authenticate users from social networks, and set up actions/triggers to publish activity on the site (including commenting) to the user's social networks.

@azinck, see #5 above:

Please put the multi-network registration capability into one button on the comments like Google Friend Connect!

Basically, if the user is not logged in and looks at the comment area, there is a set of icons allowing quick login and then comment posting. Look at some Google Friend Connect for Drupal demo.

Postponing this request on #742430: Patch to fix several bugs.

Sorry, forgot to actually change status. (By the way, I want this too - but some code cleanup is necessary first, in my opinion.)

A different approach the would make it easier to have commenting Auth functionality - add a Gigya connect widget (http://wiki.gigya.com/030_API_reference/010_Client_API/020_Methods/socia...) and use that to just connect the user for commenting.

registering the user instead, through a one-click registration process (just as a reference this use case would be based on this: http://wiki.gigya.com/001_Product_Guide/010_One_Step_Registration) wouldn't be a good experience becuase:

A) The Drupal user entry created would be totally empty
B) that user will no longer be able to register with that Social identity, because the identity will already be "locked" with the empty user entry created in the Drupal DB.

Itamar: I think I understand what you're saying. So using the basic socialize.connect method, we could authenticate a user with a social network, so that their comments would be associated to that social network identity (like how the Disqus module does it - http://drupal.org/project/disqus; see Mashable.com for an example).

But socialize.connect wouldn't provide all the necessary information to create a Drupal account as a one-click process, as described on the other page you linked. There would have to be an additional step, in a pop-up window or modal dialog, to get the email address, so that it could be added to the user's DB record.

Am I understanding you correctly?

It seems, though, that if people didn't care if their sites' users could link other accounts to their Drupal account, or log in using the Drupal credentials, then you still could have 1-click registration. (Kind of like how Disqus does it, except the 1-click registration would be on the Drupal site, instead of on the Disqus system.)

@decibel.places: Yes, that makes sense. The most one would probably be able to do with anonymous commenting would be to get user profile picture, username, and social network link to show up at the top of the comment (a la Disqus), but not to make that a full registration process. Registration would still be multi-step.

suscribe

subscribing

This probably needs more thought before it would be added. Some sites might want a two-tiered linkage system, where commenting was separate from registration, but most probably do not.

Using the latest -dev, I was able to add the Gigya loginUI to a comment form using the following code in a custom module:

function MODULENAME_form_comment_form_alter(&$form, $form_state) {
  global $user;
  if($user->uid == 0) {
    $form['name']['#weight'] = -1;
    $form['gigya_login'] = array(
      '#weight' => 0,
      '#value' => '<div id="gigya-register">' . theme('gigya_login_block', 'comment_form', TRUE) . '</div>',
    );
  }
}

Note that in my template.php, I have overridden the gigya_login_block function as follows:

function THEMENAME_gigya_login_block($form_id = NULL, $suppress_title = FALSE) {
  $login_div = gigya_login_ui_js();
  $output = '';

  if (!$suppress_title) {
    $title = t('Login using social networks');
    $output = '<h2>'. $title .'</h2>';
  }
  else {
    $output = '';
  }

  $output .= '<div class="use-text"> or use </div><div class="gigya-login">' . $login_div . '</div>';
  return $output;
}

This way, there is the Name: "Anonymous" form element, then on the next line "or use" and the Gigya login icons.

If the registration process prepopulates their data (which I'm not entirely sure happens anymore), then they could click the icon of a service that provides that feature, and they would automatically have an account.

However, the way Gigya works currently, all logins are redirected to a page (either "user" or one that the administrator specifies). For this functionality to work properly, there would need to be an option to redirect back to the page from which the user registered.

Also, this works for the case in which you want users to register via Gigya, and then comment. Pulling an anonymous user's social network info, but not creating an account for them, as discussed in #'s 13-16 would be a different workflow, and would require different function calls, and possibly a different widget, so the UX expectations were clear as to what would happen when a user clicked a social network icon. However, we might want to support both cases: registration of users, and anonymous commenting with social network icons. I've seen both forms of SN integration on the Web.

Finally, if we want to have registration for the social network services that *do not* prepopulate the fields, it might be best to do that in a modal dialog, rather than to have them go to a separate page. That way, the user's original context is not lost.

Attached is a screenshot of what the Gigya login on a comment form looks like, at least currently. Obviously, more work could be done in the theme layer.

Thanks for your work on this, Evan. This is outside the scope of what I'm working on right now but is important.

As we reevaluate the Gigya module's API I'll be sure to implement more flexibility and/or intelligence in the destination parameter.

@azinck: Ah, that makes sense. I might disable the destination parameter functionality in my copy of the module for now, then, or else change it so it redirects back to the page that a user was on.

Feel free to set back to postponed if you want. I just wanted to share with you my progress, especially since I saw it on the roadmap.

subscribe - this is looking really good.. any new progress?

sub

Anyone having problems with creating an account using Gigya Connect/Login and then comment fields not appearing on user profile pages? I'm using advanced profiles, and as long as I create an account by creating a user name and password and then later linking my accounts via Gigya, comment fields and boxes appear on user profile pages. However, when an account is created through Gigya, those fields disappear. Something to do with auto roles, perhaps?

RcLRaptor:

Are you using an auto role assigner module?

I'd love to have this too, will work on a similar patch to the 3.x version, so bumping it up.

I've added the gigya login prompt to the comment form, patch attached.

@jenlampton: #30 seems like an elegant way to do it. Just one suggestion: could it be controlled by a variable? Some people might not want multiple instances of the Gigya login form on a single page.

(I haven't been engaged with this lately, since to upgrade to 3.x of Gigya would require me to forward-port some of the changes I had made to 2.x back in the day.)

agreed. I think the way to handle all these features is via separate modules, actually. With separate config. I'm working on a patch to add the Gigya ShareBar as another dependant module, I'll rework comments with it's own settings in the same way, if I get time.

Gigya's 6.x module is deprecated. We no longer support this version and we encourage upgrading to our latest module.