Gigya provides people with an opportunity to comment on your site via other social networks - so if they don't have an account on your site, or aren't logged in, they can still comment via Gigya - instead of via Drupal.
A Description of the comment plugin can be found here:
http://www.gigya.com/platform/engage.aspx
| Comment | File | Size | Author |
|---|---|---|---|
| #8 | gigya-comments.patch | 6.18 KB | gambaweb |
| #6 | rework_comments_plugin_with_width_support-1110094-6.patch | 8.52 KB | jenlampton |
| #5 | rework_comments_plugin-1136110-5.patch | 8.19 KB | jenlampton |
| #1 | comments_plugin_support-1136110.patch | 7.15 KB | jenlampton |
Comments
Comment #1
jenlamptonHere's a patch with a new sub-module.
Comment #2
Nick Lewis commentedOne suggestion: Stream ID more or less means "content id". If you are able to pass the current nid (through menu_get_object() or nodeapi) to Drupal.settings.[x] then this block will work like a regular comments block for nodes.
Comment #3
gambaweb commentedjen thanks for the patch I'm just working on adding the same functionality
so I'll try and merge the two sub modules
Comment #4
jenlampton@gambaweb - I'm sorry I didn't find the other issue. Can you add a link here so we aren't duplicating work?
@Nick Lewis - according to their documentation the "Stream ID" is really a URL (they called it a permalink) - but since Drupal's aliases aren't really unique identifiers, I think node ID is the most sensable match... *except* when you are using these comments in a block on every page, which happens to be my use case. :(
Since blocks are dumb, and I cant have a global comments stream in the sidebar, *and* a node-specific comment stream at the bottom of each post, I think I'm going to provide two blocks instead of just this one. Then I can have them each in a different place. This one I'll rename "Global" and the other I'll call "Content". In theory, we could also have one for "User" or "Term" or anything else with a unique ID in drupal.
Thoughts?
Comment #5
jenlamptonHere's a new patch that includes an additional block for nodes, and one for users.
Comment #6
jenlamptonThis patch includes width settings in the block config, so the inline css Gigya provides won't break your site :)
Comment #7
Nick Lewis commentedJen, I agree with your approach. This patch looks great.
Comment #8
gambaweb commentedsorry for the late response I was a bit busy.
I'm attaching my implementation (haven't got to merging them both).
the basic idea here is to replace the default drupal comments with the gigya comments and every comment that gets posted via gigya will be added to the drupal comments via ajax.
that way if someone whats to remove gigya from his site he will still have the comments.
@Nick Lewis I talked to the gigya people and there is no problem having the nid being the StreamId as stream ids are per domain we don't have problem of them conflicting between (if you have a few drupal sites).
that is how implemented it.
there is still a bit more work to be done
Comment #9
colzbox commentedCan somebody please update this patch #6 for 7.X ?!
Comment #10
gambaweb commentedthere is a Gigya comments module in D7
Comment #11
demonrage commented@gambaweb
why not making this patch as tar or .zip module, cause there are lot of newbies (including me) that don't know how to create a module in drupal