Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.We need better documentation for OpenID Content Profile field. This preliminary patch updates .info file and README file. We should further provide solid INSTALL instructions and a description of what behavior can be expected:
* Does openid_cp_field create a content profile when not available?
* Does openid_cp_field only work on registration or also when adding an openid to an existing account?
* Once OpenID field information has been added to a profile, how can it be updated?
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | openid_cp_field_doc.patch | 3.96 KB | alex_b |
| #2 | openid_cp_field_doc.patch | 4.61 KB | aron novak |
Comments
Comment #1
aron novakJust for sure, I document the things here before writing the README.
* Does openid_cp_field create a content profile when not available?
openid_cp_field examines if there is a profile node for that user. If it exists, it does nothing. If there is no profile node, it creates the profile node.
* Does openid_cp_field only work on registration or also when adding an openid to an existing account?
It does work also when adding to an existing account. How does it work? First, add the openid to the existing account. Log off. Log in with the openid, and if you did not have a profile, your profile is created.
* Once OpenID field information has been added to a profile, how can it be updated?
There is no synchronisation yet. So if once the profile is created, it remains unchanged until the user updates it manually.
Maybe we can create a checkbox "Keep profile in sync with the remote openid personality" and then do a one-way sync (from the openid provider to the client) Bi-directional sync is a little bit more problematic because of conflicting data, i do not suggest to go on that way.
Comment #2
aron novakIt needs strong reviews to make sure that it's fluent English :)
Comment #3
alex_b commentedThank you. Will review.
Comment #4
alex_b commentedReviewed and copy edited.
Questions:
* AX specification covers SReg fields, does this mean that if AX is installed, we don't need SREG? http://www.axschema.org/types/
* I added client SReg to the documentation. Was there a reason why it was not included?
Comment #5
alex_b commentedAron, give this a last review and RTBC it if you can answer my questions right away.
Comment #6
alex_b commentedCommitted.