My log is filled with gigya_notify_login and it seems I get one log entry for every page visited.

For example, in the past 13 minutes I have:

gigya 09/16/2010 - 12:20pm gigya_notify_login admin
gigya 09/16/2010 - 12:20pm gigya_notify_login admin
gigya 09/16/2010 - 12:20pm gigya_notify_login admin
gigya 09/16/2010 - 12:18pm gigya_notify_login admin
gigya 09/16/2010 - 12:18pm gigya_notify_login admin
gigya 09/16/2010 - 12:17pm gigya_notify_login admin
gigya 09/16/2010 - 12:17pm gigya_notify_login admin
gigya 09/16/2010 - 12:15pm gigya_notify_login admin
gigya 09/16/2010 - 12:15pm gigya_notify_login admin
gigya 09/16/2010 - 12:14pm gigya_notify_login admin
gigya 09/16/2010 - 12:07pm gigya_notify_login admin

Comments

azinck’s picture

azinck commented

Can you please try v. 3? I believe this should be fixed there.

vacilando’s picture

vacilando commented

Same problem :-(

Is upgrade to v3 safe? It still says "beta"...

azinck’s picture

azinck commented

vacilando:

Yes, upgrade to v3 is safe and it's definitely an improved module. The only reason it's still marked beta is that there's no upgrade path per se, so when you install v. 3 you have to re-create any Gigya actions and Gigya profile mappings you may have set up.

vacilando’s picture

vacilando commented

You answered quickly but too late for me... I've already installed v3 and ran update.php. But login -- the only feature of Gigya I use on the given site -- seems to work fine. So only mappings don't have an upgrade path,right?

azinck’s picture

azinck commented

vacilando:

Correct, no upgrade path for mappings or actions (the way sharing is implemented in the module). Your Gigya user accounts will still work fine.

robcolburn’s picture

robcolburn commented
Issue summary: View changes
Status: Active » Fixed

Closing issue

robcolburn’s picture

robcolburn commented
Status: Fixed » Closed (fixed)