Document Gigya Profile2 integration using Gigya Default Token module

Subscribing. I'm interested in this as well.

The basic Gigya user is tokenized so a few solutions:
put gigya tokens as default values in your profile2 fields
1. write a field view formatter that does token_replace to the filed text.
2. use "Token Filter" http://drupal.org/project/token_filter
3. do the token_replace in your filed theaming function.
I just updated the tokens in the dev version

added a sub module in dev.
I'll be glad to get some use cases so we could improve it.
please read the README.txt file

I should write a better README file
The module creates a "gigya default profile" with the fields from the default fields from gigya user object you can add extra fields that are in the gigyaUser object defined as extraFields here http://developers.gigya.com/020_Client_API/020_Methods/socialize.getUser...
this the comma seperated list.
there is a hook_gigya_profile2_create_profile_type that fires when the default profile is created.
the module populate the fields.
there is a hook_gigya_profile2_alter to add stuff to the profile when it is created.

it creates a new instance of a profile2 type "gigya_profile"

You apparently have to use the gigya_profile bundle type in order for the Profile2 integration to work correctly. gambaweb, is that correct?

Changing to a documentation task since the support is there, even if there could be more added. Janrain seems to have a more flexible integration with Profile2 presently, and can also integrate with fields on the User entity.

yes you should use gigya_profile bundle
we are working on a better implementation

@gambaweb: Does this mean that the gigya_profile fields will soon be deprecated? Do you have a projected release date for a new implementation of this integration? I ask so I know whether to rely on these as part of my IA.

yes gigya_profile will be deprecated the new implementation will let you have a default value for a field as a gigya token
regardless of where the field is profile2, user etc...
about the release date I'll update this issue as soon as I'll know. it should in the next 2 week or so

attached is a patch that adds gigya user info as default values in the gigya_default_profile profile2 editing form

@gambaweb:

Is the Profile2 integration coming back into the Gigya module soon? We will need it in the next week or so (2 at most) for a current project. If you aren't planning on doing it by then, we will need to create something custom.

Would the old Profile2 integration work with the newest release of the module?

we have new implementation of profile2 (or any other text field) in the 7.x-4.x version it gives you the ability to set gigya token as a default
value for a text filed. in the new version you can use text fields on the user page and not only profile2
the patch above works in the same way only that it works only with profile2

EvanDonovan, please try our new version and tell us what you think. We plan to release it as an official version soon. There are no currently known issues in it.

Thanks for letting me know that that is the intent of the Gigya Default Token module. I was unaware. Can that be documented more - perhaps it would even be helpful to state that is one of the use cases of the module in the description on the modules page.

I have tested it now, and it does appear to be pulling over some of the information when I set the default token value for a field. However, if there is a field with no data, it seems to trigger a PHP notice like, "Notice: Uninitialized string offset: 0 in text_field_widget_form() (line 510 of /drupal/modules/field/modules/text/text.module)." I can report that as a separate issue if you wish.

Evan can you please post the steps to reproduce

Two bugs I've observed with Gigya Default Token so far. The latter is more serious.

• #1720756: PHP notice when Gigya Default Token attempts token replacement for a social network login which doesn't provide that token
• #1720770: Gigya Default Token values are not preserved on profile edit

We can deal with those bugs in their respective issues; this one will be for the documentation of the Gigya Default Token module.

please change in recent version reopen if still relevant