I have managed to exchange profile information when using normal text fields, but should this module work with other field types also? If I try to define some field to be a link field in the relying party side, the field is not filled with information. I'm using computed field on the provider side for links to the profile and profile picture.
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | support_link_field_fixed.patch | 1.49 KB | merilainen |
| #2 | support_link_field.patch | 1.42 KB | merilainen |
Comments
Comment #1
merilainen commentedI managed to exchange date type, so the problem I currently have is only with the link field. It's probably because that field is different from other fields, because it has separate fields for url, title and attributes in the database. All the other CCK fields seem to have _value field for the actual data, which doesn't exist for the link CCK fields.
Comment #2
merilainen commentedI got this working by modifying the module to check also url field from database instead of only reading value field. I haven't tested this much, but it seems to work with a trivial homepage field which I have used on both relying and providing sides.
Comment #3
darren.ferguson commentedYeah this module code needs to be re-verified in the module, patch looks good, but definitely looking at getting the module over hauled so it can support any content type field out of the box.
Comment #4
merilainen commentedYea, I did this patch to match my needs, but there is some problem because after this patch it only transfers the url fields. I cannot figure out why, since my php knowledge is not on a jedi level. The if sentence below seems to return true always, so it never gets the value field in the else branch:
Comment #5
merilainen commentedFound the problem, it was in _openid_cp_field_populate_field(), where I check if the field is a link field. Now it works with this fixed patch, but more testing should be done.