Hi,

I spoke with Eddy at Gigya and told him I would post this issue here.

I am noticing that Drupal will do a full page load with standard Drupal comments and then the Gigya JS will delete the Drupal comments and then replace them with Gigya's comments. This has performance implications as well as a degraded user experience.

I have linked to a video (can't upload .ogv files) of the behavior on a 3G connection, this slows the load down so you can see this better as it is not as evident on a high bandwidth connection, although still evident.

Comments

gambaweb’s picture

this is only the default behavior all you have to do is disable drupal comments and add a div with the id you configured in the comment plugin configuration page, and the Gigya comments will be displayed there.

elijah lynn’s picture

I guess this will do as a workaround.

Thanks

sokrplare’s picture

Cross referencing #1867194: Unset comments when container ID other than Drupal "comments" is chosen.

Liran / gambaweb - do you know if Gigya's comments will still be stored as Drupal comments if Drupal comments are turned off per this thread's recommendation?

elijah lynn’s picture

They definitely will not be stored if the Comment module is turned off.

sokrplare’s picture

That's what I thought - so this isn't a great workaround from that standpoint. Will take the conversation back to the other thread then - thanks Elijah!

gambaweb’s picture

the way it is implemented now is that on click on the gigya comments there is an ajax call to store the same comment in drupal.
this for 2 reasons:
1. if some one just want to try the gigya module he won't lose his comments.
2. SEO when a web crawler crawls the site it could index the comments to.
so the comments module should me enabled.
if you want you could hide the node/node_type settings. if you want the comments to be stored in drupal.

gambaweb’s picture

there is a fix in the latest DEV version see
http://drupal.org/node/1867194

gambaweb’s picture

Status: Active » Closed (fixed)