The other week when I spoke with Gigya technical support, they said that the Drupal module was designed so that it would save the comments to the Drupal database, even if they were being posted to the Gigya system via the Gigya commentsUI that replaces the regular Drupal comments div.
However, I was never able to get this to work in the 7.x-3.2 branch, and now having upgraded to 7.x-4.x, I still cannot get it to work.
In 7.x-4.x, I see that the function that does this work is gigya_comments_ajax(), which takes information that is being posted to Gigya, and turns it into a comments object, then calls comment_submit() and comment_save().
I've tested saving comments while logged in to Gigya though and it did not actually save them to the comment table in the Drupal database.
If you're not aware of this issue or what might cause it, I might be able to debug it further for you.
One somewhat related issue that I'll mention briefly:
It appears that since the Gigya commentsUI replaces the Drupal comments div, any comments that are in the Drupal database only will not get displayed when Gigya is enabled. Is this correct? If so, are there any plans to change this?
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | 1598708_json_output.patch | 594 bytes | gambaweb |
Comments
Comment #1
gambaweb commentedI'll check and see way the comments are not saved.
replacing drupal comments is just the default you can put it in any other container and have them both.
Comment #2
gambaweb commentedok checked on a plain drupal install and it worked of me.
on thing that could case this is that there is a validation check that comment came form gigya (line 123)
you can see if the comment was valid of not from the return code
attache is a patch that changes the return from drupal_json_encode to the right drupal_json_output so we won't get a html page back
Comment #3
EvanDonovan commentedSorry for not checking back sooner. We were working on other aspects of the project development. I will test your suggestion in #2 today.
Regarding your comment in #1, are you saying that when you specify which div to target, it is possible to say that you want to target a different div so both comments sections would show up? That would be useful, although in our case, I think that the potential confusion from having two comments sections would not be ideal.
Comment #4
EvanDonovan commentedI'm not seeing this issue anymore in 7.x-4.0, so closing.